@JuliaDaehne we are looking for the following two API scopes to choose in the migration UI but they are not available:
-
read:issue-details:jira(required by POST /rest/api/2/search) -
read:issue-meta:jira(required by GET /rest/api/2/issue/createmeta)
Some feedback for the team:
From my first impression, I really struggle to make sense of this migration UI.
-
Why does it count the same scope so many times when I select it in the UI? Let’s say I need the
read:issue:jirascope. When I select this scope in the UI it counts it multiple times. Not really sure how this information is helpful. From my research, we need 29 of the new scopes in total. The list for “View Jira issue data” alone shows 51 new scopes added
-
We have different OAuth apps for development, test, staging, and production. Selecting scopes one by one for each app is really slow. It would be so much easier if we could just paste the list of scopes we require. Because the migration UI does not provide any assistance with compiling required scopes, we anyways have to manually prepare the list of required scopes on the side.
Here is what I would have expected the migration assistant to look like:
A list of API endpoints where I can select the ones we use and the migration assistant will compile the deduplicated list of required scopes for me.