Correct lookup of issuetypes when calling create_issue #978
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
adehad added enhancement Status: Ready 
Contributor
| @soerenbe if you are able to merge the latest master and then address the errors raised during |
Contributor Author
| Thanks @adehad for having a look at this issue. I fixed the syntax error. |
adehad approved these changes May 15, 2021
svermeulen pushed a commit to svermeulen/jira that referenced this pull request Oct 31, 2021
* correct lookup of issuetypes when calling create_issue * Fixed syntax error for issue 978
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
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.
Today I got the issue that there where 2 issuetypes with the same name in our Jira installation. The current implementation have 2 issues with this:
1.) It always picks the ID of the first matching name. This may result in a error during create_issue because the other issuetype ist not available in that project. In this case I now raise an Exception beause the request of create_issue is not clear.
2.) When providing a issuetype id
create_issuenot correctly uses this value.