Get rid of the third-party jira dependency.
Review Request #15480 — Created Nov. 11, 2026 and updated
The JIRA integration needed the third-party
jirapackage (and
requests), which wasn't a dependency. Admins had to install it by
hand. Without it, JIRA quietly did nothing. This was extra silly because
we only used a very small number of API calls from it.This change replaces that with a new
JIRAClientimplementation that
uses our own HTTP layer.The behavior is the same as before:
- The account's credentials are only sent to the account's own server.
Legacy URLs on repositories are still contacted anonymously. - Requests time out after 10 seconds.
- JIRA Cloud uses the search/jql endpoint, since Atlassian removed search
there. The jira package used to automatically pick this for us. Cloud is
detected by the *.atlassian.net domain.
A few things are improved as a result of using our HTTP layer:
- Certificate errors when connecting an account now reach the usual "trust
this certificate" flow instead of failing. - Issue keys are escaped in request URLs.
- Errors in the batch issue lookup are logged instead of being raised.
- Ran the JIRA, hosting service, and connected services admin tests.
- Interacted with a JIRA cloud bug tracker with searches and infoboxes.
| Summary | ID |
|---|---|
| qwnvsyvvwvkxnyyxntpklpsvwrqqzorz |
| Description | From | Last Updated |
|---|---|---|
|
Seems weird for this error message to end in a colon and empty space. Can we make the fallback message … |
|
Review request changed
- Commits:
-
Summary ID qwnvsyvvwvkxnyyxntpklpsvwrqqzorz qwnvsyvvwvkxnyyxntpklpsvwrqqzorz - Diff:
-
Revision 2 (+3290 -1810)
Checks run (2 succeeded)
flake8
passed.
JSHint
passed.