Adding toolsets#123
Conversation
iosamaatlassian
requested review from
SreeNerella,
blakewang-atlassian,
dvenkatesh07,
ekahinga,
jatinkrmalik,
jvarghese2 and
lsosa1
as code owners
| | `SEARCH_JIRA` | Search Jira issues using JQL | OAuth + Headless | | ||
| | `READ_CONFLUENCE` | Get pages, spaces, descendants, ancestors, footer comments, inline comments, comment children | OAuth + Headless | | ||
| | `WRITE_CONFLUENCE` | Create pages, update pages, create footer comments, create inline comments | OAuth + Headless | | ||
| | `SEARCH_CONFLUENCE` | Search Confluence content using CQL | OAuth + Headless | |
There was a problem hiding this comment.
hey @iosamaatlassian should we expose supported oauth types for these capabilities/toolsets? this is more internal for admin controls
There was a problem hiding this comment.
Or maybe it does make sense, because I had split them up based on what tools are rolled out by each auth type, so yes we can do the same mapping here
There was a problem hiding this comment.
For admins, we shouldn't really IMHO. The capability here is just a tool filter technique not an actual permission.
|
|
||
| ### Capability compatibility by authentication mode | ||
|
|
||
| Capability availability also depends on authentication mode: |
There was a problem hiding this comment.
considering this is because we dont have some tools supported in oauth and headless, is this distinction necessary to clarify or would it confuse them more?
also considering we will have a toolset selection at consent for oauth, how does this work when we rollout new consent, then there would be 3 levels of filtering for oauth flows?
There was a problem hiding this comment.
We have this distinction in our tool docs already. In this experience it's better to state this until we support all scopes under all auth methods.
Folks might see Toolsets for JSM and might not know why it's not showing for them.
|
|
||
| | Capability | Enables | Supported auth mode | | ||
| | --- | --- | --- | | ||
| | `READ_JIRA` | Get issues, projects, transitions, issue type metadata, worklogs, remote links | OAuth + Headless | |
There was a problem hiding this comment.
@iosamaatlassian are we not having these for TWG tools yet? we are calling it read_atlassian and write_atlassian.
2 participants
Rovo Dev code review: Rovo Dev has reviewed this pull request
Any suggestions or improvements have been posted as pull request comments.