Improve error handling and fix support for adding a watcher to the Jira ticket#14
Merged
Improve error handling and fix support for adding a watcher to the Jira ticket#14
Conversation
JasperCraeghs
changed the title
4 tasks
Member
|
Should we also keep support for jira <3.2 ? Or you think audience is small enough on self-hosted Jira space to justify complete removal? Then we should at least check or enforce API somewhere, to make sure we are compatible? |
Member
Author
|
jira <3.2 refers to https://pypi.org/project/jira/#history, and it's not made by Atlassian. Based on the discussions in their PRs, they keep support for Jira Server active. |
Letme
approved these changes
Jun 23, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
accountId, so I that we don't need to. Therefore, I have removed that code.