Fix Jira issue search by using go-jira fork #135
Merged
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
jadolg
requested changes
Sep 5, 2025
jadolg
approved these changes
Sep 5, 2025
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.
Jira changed their API, and now things are broken: andygrunwald/go-jira#715
There's a PR open to fix it: andygrunwald/go-jira#724, but it's not merged yet.
To get Jelease working again then let's use this branch in the meantime, and switch back to the main branch once it's merged.
This has been tested by manually building an image and running it in prod. Then in our webhookrelay I could resend some older events, and I saw Jelease (running the code from this PR) successfully be able to both create new Jira tickets as well as find and update older tickets.