Jira Service Management permission resolvers with unit tests #58
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dxu2atlassian
changed the title
dxu2atlassian
force-pushed
the
feat/EAS-2547
branch
from
b54ce6e to
a4962f8
Compare
dxu2atlassian
force-pushed
the
feat/EAS-2547
branch
from
a4962f8 to
21c6b7e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Draft of JS and JSM permission resolvers. The JSM works as expected and the unit test passes, similar to the Bitbucket addition on the other PR. However, for now, the Jira Software parsing doesn't work as the swagger document doesn't seem to have the "x-atlassian-oauth2-scopes" that is utilized.