[JIRA] JIRA Issue Details Blank Page

[ebresie]

When reviewing "My issues, it shows the list of JIRA tickets but when clicking on the item, a blank Jira Issue page is opened up.

I believe this is related to BitBucket ticket](https://bitbucket.org/atlassianlabs/atlascode/issues/351/jira-issue-details-blank-page)

Not sure if this is the issue but I suspect the API used currently may have been deprecated/replaced and may be as simple as changing to the correct API reference where applicable.

[ebresie]

With the new tracking on Github, I wasn't sure what the process to get existing tickets was so figured I would start a new ticket here and have things acted on here. If work for this is to continue on the Atlassian BitBucket site, then this can be closed as duplicate but would still want updates to be made to fix the problem.

[sdzh-atlassian]

Hi @ebresie!

Thanks for carrying the issues over here! You're right in assuming that we'd be tracking things here in Github now 😄

We're still getting our bearings in the codebase - but this feels like an issue caused by the client we're using to fetch the data going out of date. We'll see what we can do! I'll keep you posted when any changes are made

[georgespano]

More info about this issue and the respective work around can be found here: https://bitbucket.org/atlassianlabs/atlascode/issues/753/cannot-open-issue-create-issue-in-vscode

[dgrierso]

I suspect that this is related to this issue which I raised on BitBucket which hasn't been transferred across to GitHub:

https://bitbucket.org/atlassianlabs/atlascode/issues/5435/bug-in-getcreateissuemetadata-for-data

Original defect details added below:

The @atlassianlabs/jira-pi-client library which is used has a defect in it which is preventing this plugin from functioning with Jira Data Center instances.

The REST API for getting issuetypes associated with a project on a Jira DC instance is: issue/createmeta/{projectIdOrKey}/issuetypes but the client code within the @atlassianlabs/jira-pi-client library appears to be attempting to construct a URL of the form: issue/createmeta/{projectKey}?expand=projects.issuetypes.fields

The latter API call is valid only for Jira Cloud instances.

See the following API calls on my DataCenter instance:

10.105.64.251 - - [08/Nov/2024:09:52:43 +0000] "GET /rest/api/2/issue/createmeta?projectKeys=CBST&expand=projects.issuetypes.fields HTTP/1.1" 404 54 "-" "atlascode/2.x axios/0.19.2"
10.105.64.253 - - [08/Nov/2024:12:17:13 +0000] "GET /rest/api/2/issue/createmeta?projectKeys=CBST&expand=projects.issuetypes.fields HTTP/1.1" 404 54 "-" "atlascode/2.x axios/0.19.2"

As you can see these are receiving a 404 response - which causes the issue loading screen in VSCode to break completely and appears as a blank window.

I would report this as an upstream issue but the jira-pi-client repository no longer appears to exist at its published location:

• https://bitbucket.org/atlassianlabs/pi-clients/ reports that is now at /~https://github.com/atlassian-labs/pi-clients
• /~https://github.com/atlassian-labs/pi-clients gives a 404 for that repo

If the underlying jira-pi-client repo is not maintained then the Atlascode plugin should either:

1. Take over maintenance of it so that their plugin is maintained properly;
2. Port Atlascode plugin to use a different library which is maintained.

---

End users can fix this by modifying their $VSCODE_HOME/extensions/atlassian.atlascode-$VERSION/build/extensions/extension.js file to modify all occurrences of :

From : this.getFromJira("issue/createmeta",{projectKeys:[t],expand:"projects.issuetypes.fields"})

To : this.getFromJira("issue/createmeta/".concat(t,"/issuetypes"))

However this must be done for every version of Atlascode which is released.

As you can see after modifying the file the issuetype retrieval call is successful:

10.105.64.251 - - [08/Nov/2024:09:52:43 +0000] "GET /rest/api/2/issue/createmeta?projectKeys=CBST&expand=projects.issuetypes.fields HTTP/1.1" 404 54 "-" "atlascode/2.x axios/0.19.2"
10.105.64.253 - - [08/Nov/2024:12:17:13 +0000] "GET /rest/api/2/issue/createmeta?projectKeys=CBST&expand=projects.issuetypes.fields HTTP/1.1" 404 54 "-" "atlascode/2.x axios/0.19.2"
10.105.64.254 - - [08/Nov/2024:14:49:12 +0000] "GET /rest/api/2/issue/createmeta/CBST/issuetypes HTTP/1.1" 200 3471 "-" "atlascode/2.x axios/0.19.2"
10.105.64.252 - - [08/Nov/2024:14:50:41 +0000] "GET /rest/api/2/issue/createmeta/CBST/issuetypes HTTP/1.1" 200 3471 "-" "atlascode/2.x axios/0.19.2"
10.105.64.253 - - [08/Nov/2024:14:50:44 +0000] "GET /rest/api/2/issue/createmeta/CBST/issuetypes HTTP/1.1" 200 3471 "-" "atlascode/2.x axios/0.19.2"

[sdzh-atlassian]

Thanks for digging into this further folks!

You are right in that we have observed several issues related to that client package already - and you are also right that we aren't the team maintaining it right now 😄

Still, there might be some things we can do to address these issues in the existing client - which is what we're looking into to hopefully address these.

[dgrierso]

Problem still exists in version 3.2.3, although now you receive the notification:

Corresponding HTTP logs are:

10.105.64.254 - - [27/Jan/2025:11:55:30 +0000] "GET /rest/api/2/field HTTP/1.1" 200 179310 "-" "atlascode/2.x axios/0.19.2"
10.105.64.252 - - [27/Jan/2025:11:55:30 +0000] "GET /rest/api/2/issueLinkType HTTP/1.1" 200 1845 "-" "atlascode/2.x axios/0.19.2"
10.105.64.254 - - [27/Jan/2025:11:55:30 +0000] "GET /rest/api/2/issue/CBST-11121?expand=transitions%2CrenderedFields%2Ceditmeta%2Ctransitions.fields&fields=*all HTTP/1.1" 200 171335 "-" "atlascode/2.x axios/0.19.2"
10.105.64.250 - - [27/Jan/2025:11:55:31 +0000] "GET /rest/api/2/issue/createmeta?projectKeys=CBST&expand=projects.issuetypes.fields HTTP/1.1" 404 54 "-" "atlascode/2.x axios/0.19.2"

[dgrierso]

This looks like it may be fixed in version 3.4.0

[lutin-malin]

Confirmed as fixed in 3.4.0

[bwieger-atlassian-com]

Closing this one out.

Let me know if you are still experiencing the issue on versions >= 3.4.0

[ebresie]

Confirm it works for me as of 3.4.0