Add the "option" field type for custom fields #71
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
JIRA supports SelectList field types, which are similar to but represented not quite the same as Strings. This change allows go-jira to create issues with custom fields on them that are SelectLists.
|
Thank you :) |
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.
What does this PR do?
JIRA supports SelectList field types, which are similar to but
represented not quite the same as Strings. This change allows go-jira
to create issues with custom fields on them that are SelectLists.
Why?
I had to create an issue in a project that heavily templates issues with custom fields, and it's making use of the "SelectList" type a lot. This was the only way I could get it to work on our installation.
I hope you find this PR acceptable - happy to fix anything that's wrong with it (: