[MM-794]: Fixed the issue of fields not prefilled when creating issue with custom fields #1127
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
raghavaggarwal2308
added
2: Dev Review
wiggin77
reviewed
Oct 22, 2024
| q.Add(key, id) | ||
| } | ||
| case []interface{}: | ||
| for _, element := range fieldTyped { |
There was a problem hiding this comment.
@Kshitij-Katiyar can you add some comments indicating what field type(s) each case represents.
There was a problem hiding this comment.
@wiggin77 Added the comment for what fields are handled in each case.
please have a look
wiggin77
requested changes
Oct 22, 2024
|
/update-branch |
wiggin77
approved these changes
Oct 28, 2024
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.
Summary
Fixed the issue of fields not being prefilled when creating issues with custom fields. Unable to support the fields related to the users because the Username is not available in the create issue data and all the user picker fields on the Jira create issue form work on the username.
Added Support for:
Fields still not supported
Issue link
Fixes #794
Video Link
https://flonnect.com/video/6d26327abd0d-4a7d-855a-3f4c909e8648
How to test