Fix User-type fields for Jira Server on first revision #899
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
Jbekker
changed the title
|
This issue is resolved for Jira Cloud with #873 but that fix was not complete to also work for Jira Server. |
Alexander-Hjelm
changed the base branch from
master
to
bugfix/fix-user-picker
Merged
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.
On Jira Server there is no accountId property on a user picker field, we should use the name property instead like how it's done for the assignee, creator and reporter fields.
Without this fix, the value for a (custom) user picker field is only set correctly through the changelog but not on the first revision.