Skip to content

Switch to the Atlassian Jira Cloud instance and API#390

Merged
TomasTomecek merged 1 commit intopackit:mainfrom
antbob:jira-cloud
Mar 23, 2026
Merged

Switch to the Atlassian Jira Cloud instance and API#390
TomasTomecek merged 1 commit intopackit:mainfrom
antbob:jira-cloud

Conversation

@antbob
Copy link
Contributor

@antbob antbob commented Mar 19, 2026

As we have recently migrated to Jira Cloud from Jira Data Center this set of changes is needed to make Jira related functionality to work. Originally i wanted to keep both working (this being open source project and all) however it is not feasible for me to do so due to the old Data Center instance no longer fully functioning to do any testing and just the time constraints associated.

The major changes are:

  • Switch Authentication: Bearer to Basic Auth as the former is no longer supported.
  • Switch Search endpoint from /rest/api/2/search to /rest/api/3/search/jql as v2 is no longer supported.
  • Switch to v3 API where possible and stay with v2 API where supported and switch to v3 is too complex.
  • Switch to Jira dev-status API from BitBucket API as the later is no longer supported in our cloud instance.

This has been tested for Jira issue fetcher, Triage and Backport agents, specifically that they can search and retrieve issues, add and remove labels, add comments etc. I have not done any real life testing for Supervisor except a few curl tests, we're currently not using it so it is hard for me to verify it on anything real.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request successfully migrates the Jira-related functionality from Jira Data Center to Jira Cloud, addressing several key changes. The authentication mechanism has been updated from Bearer to Basic Auth, and the Jira search endpoint has been switched to the v3 API. Additionally, the Jira dev-status API is now used instead of the BitBucket API for fetching development status. The changes are well-distributed across the codebase, including constants, utility functions, fetchers, and tools, and the test suite has been updated accordingly. Overall, this is a significant and necessary update to ensure compatibility with the new Jira Cloud instance.

Copy link
Member

@TomasTomecek TomasTomecek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is straightforward, thank you, very nice work!

# Get the dev-status summary first to discover valid applicationType values
summary_url = urljoin(
jira_base,
f"rest/dev-status/1.0/issue/summary?issueId={issue_id}",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

great to see there is a replacement

data:
JIRA_URL: https://issues.redhat.com/
JIRA_URL: https://redhat.atlassian.net/
JIRA_EMAIL: jotnar@redhat.com
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for updating the openshift configs as well

@antbob
Copy link
Contributor Author

antbob commented Mar 23, 2026

@TomasTomecek the latest push is only for supervisor/jira_utils.py which fixes some Jira Cloud restrictions that Martin has found in his supervisor related testing.

@TomasTomecek
Copy link
Member

Merging, fetcher and triage agent worked just fine for me locally. Thank you very much for addressing this so promptly.

@TomasTomecek TomasTomecek merged commit d2927e1 into packit:main Mar 23, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants