search

bitcrowd / tickety-tick

A browser extension that helps you name branches and write better commit messages
MIT License
57 stars 10 forks source link

No longer works with Jira since the last few weeks #345

Closed RKushnir closed 2 years ago

RKushnir commented 2 years ago

Hi,

I'm afraid I can't use the add-on with Jira anymore. Neither from the board page, nor from the individual ticket page. I get the "Houston, we have a problem." message. Please, let me know if I can provide any more details for debugging.

Thank you for this add-on, it saved me a lot of time and typing.

Tickety-Tick revision: 8714b5142d40c0c2d5f2a51bf867f2702463ed25

HTTPError: Request failed with status code 404
We@moz-extension://b678a3b0-e950-4360-a415-4060c764f201/content.js:2:46795
n@moz-extension://b678a3b0-e950-4360-a415-4060c764f201/content.js:2:50975
pmeinhardt commented 2 years ago

Sounds like it might be the new Tickety-Tick release or a change to the Jira API. 🤔 I don't have access to a Jira project at the moment, but I bet someone @bitcrowd does and can check whether they see the same problem. 👋🙂

Based on the error message, this seems like the most likely place to start looking: 🔎 https://github.com/bitcrowd/tickety-tick/blob/v5.0.1/src/core/adapters/jira.ts#L90

One information that could be interesting for trouble-shooting is whether you're using Jira via atlassian.com ("cloud") or an on-premise ("data-center") installation @RKushnir. 🗒️✏️ Thanks for the kind words! 💚

RKushnir commented 2 years ago

@pmeinhardt Thank you for the quick reply.

I can at least answer to the last point, it is an on-premise installation at jira.kloeckner-i.com.

RKushnir commented 2 years ago

I took this chance to try to debug a browser extension for the first time ever 👶

There is a request to https://jira.kloeckner-i.com/rest/api/3/issue/PROJ-1234, which results in a 404 response. Now I suspect the fault could be in our Jira configuration. Maybe the admins have disabled or restricted access to the API. In which case there is no way you can help me.

Also, I became curious which API the Jira itself uses to dynamically load tickets, and turned out it calls URLs like this https://jira.kloeckner-i.com/rest/greenhopper/1.0/xboard/issue/details.json?rapidViewId=111&issueIdOrKey=PROJ-1234&loadSubtasks=true&_=1653500459037.

All in all, I'm going to close this issue and try to resolve it internally. Your hint has helped me, thanks.