Jira: Add handling for errorMessages field in JSM responses #1587
Conversation
This file contains hidden or 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
cmpaul
changed the title
cmpaul
force-pushed
the
fix-jsm-error
branch
from
132fe1a to
bda5def
Compare
cmpaul
force-pushed
the
fix-jsm-error
branch
from
bda5def to
d5f07df
Compare
|
@cmpaul thanks |
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.
We are occasionally receiving errors from JSM requests like this:
{ errorMessages: [ "Field Assignee is required." ], errors: {} }This results in a
KeyError: 'errorMessage'exception.