[JIRA] JIRA Issue Details Blank Page (no bitbucket)

[manuartero]

Describe the bug
The issue details won't open when clicking on an issue

To Reproduce

Steps to reproduce the behavior:

1. Go to Jira ISSUES PANE
2. Click on any issue
3. the issue details won't open

Expected behavior
The issue detail is opened in the editor

Screenshots

check video:

Screen.Recording.2024-12-18.at.09.51.45.mov

Environment and Version (please complete the following information):

• Atlassian Plugin Version: 3.2.1

• Visual Studio Code Version: 1.96.0 (Universal)

Version: 1.96.0 (Universal)
Commit: 138f619c86f1199955d53b4166bef66ef252935c
Date: 2024-12-11T02:29:09.626Z (1 wk ago)
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 23.6.0

• Is this a local or cloud environment? local, connected to a regular jira instance
• If Cloud, Browser (chrome, safari),---
• If Local, OS (macOS, windows, linux) macOs

Additional context

I've seen this extension working actually, cant tell when did it stop working but should be some update

pasting an error from the developer tools inspector:

---

NOTE: this is different issue from

• [JIRA] JIRA Issue Details Blank Page #26

there is no BitBucket here, please do not mark as duplicated

[sdzh-atlassian]

Hi @manuartero, thank you very much for reporting this! Sorry you had to run into a bad experience 😦 We certainly won't be making this as a duplicate

A special thanks for the error from the inspector - that's actually kind of super helpful to us ;D

I couldn't reproduce this right away, but I think that might have to do with something different going on with your issues that we don't have at the moment. I also have a sneaking suspicion that it's an error coming from the JIRA clients we are using. - edit: nevermind that, I totally missed the forest for the trees on this one - the issue is most likely right here in atlascode

Just to exclude some things, could I trouble you to try reproducing this in the extension version 3.0.10? This would help us rule out any recent changes we've made. I would expect the behaviour to be the same - but let's see what actually happens 😉

Installing a specific version (3.0.10 in this case) can be done in the Uninstall dropdown:

If that's too much trouble - no worries at all, thanks for the data you already gave us

In the meantime, we can look further into the client code and try some things on our end

[sdzh-atlassian]

Ok so this is kind of super weird - and I'd kind of really love to dig further into this to really figure out what's going on :)

Unfortunately, I can't seem to repro this at all - but I've made a small band-aid PR to hopefully dig this a bit further

Edit: to go into a bit more details on why this feels weird - looks like what's causing the problem here is that the summary field is somehow missing 🤔 However, summary is the issue name, and should be always required - and it looks like issue names render just fine in the sidebar?

I'd really like to know what happens if we bypass the problem with rendering the header. Are other fields also missing? Did the data to initialize the page not get passed properly? Sorry, I wish I knew the codebase enough to just root cause this outright 😁

[manuartero]

Hi @sdzh-atlassian
thanks for the support, so , let's try to give you more valuable info.

1. switched to the version 3.0.10 as requested:

2. I've added breakpoints trying to narrow the problem:

• a is react itself, no doubts.
• the problem is this, this.state is {}, and it's expecting width property
• state.width is undefined and the rest of the code is relying on having there width (undefined.uiType...)

Hope this helps (exported as 480p to be able to link here the video)

bug-report-480.mov

[manuartero]

The video quality is quite low honestly, so this is the transcription of the key part:

{ key: "render",
 value: function () ......
   ....
   return k.a.createElement('div', ae()(), a(this.state.width), e)

the key part is that this.state is {}

[sdzh-atlassian]

Hello @manuartero! I really appreciate you following up with us, and digging into this!

A separate thank you for looking at 3.0.10 - to be honest, I'm a bit relieved we can rule out our recent changes 😁

Hmm, this is super interesting - I think I encountered an issue with state.width before, IIRC due to some top-level component not working properly? 🤔 Will need to dig into that a bit further - perhaps it's something I'd be able to observe and reproduce locally.

In the meantime, a small update - I was able to repro your original error with the exact stack trace, and made a sort of a band-aid in #48. The page would now skip rendering whatever field is causing a problem, and console.err a bit of context like this:

It should be available in our most recent pre-release, 3.3.4. Could I ask you to give that version a try, to see what happens? Given the new information you found - I suspect we would see that all fields fail to render, and the page still fails in a different spot - but would be great to have a confirmation 😁 Or, who knows - perhaps something new might happen?

To install a pre-release, there's a button on the extension page:

In theory, it would pull the latest version - which right now is 3.3.4, so no futher actions would be needed after this

[manuartero]

there is a pre-release from some hours ago ? v3.3.7 ?

[SimeonBBorisov]

Hi @sdzh-atlassian ,

Are there any news regarding this issue? I'm also having this exact problem.

[sdzh-atlassian]

Hi folks! 😄 Sorry about the lack of updates, we're still returning from holiday breaks.

@manuartero - you're right! Our pre-releases are on a daily schedule, so the latest now is something like 3.3.23. The change i mentioned would be in any of them starting from 3.3.4, sorry about not being explicit earlier.

@SimeonBBorisov - hello! :) Sorry to hear that you're also having this issue. For this specific problem, there's a small stop-gap solution in the pre-release (PR #48) to help us root cause this, since I can't reproduce the problem on my end.

Unfortunately, it seems that the pages can break for a bunch of reasons - but at least one of them should be covered. Could you also try to reproduce this in the latest pre-release to see if anything works differently?

[lcatton]

@sdzh-atlassian I am having the same issue with the on premise Jira server 10.3.1 (no bitbucket), using the 3.3.23 pre-release vscode plugin.

[sdzh-atlassian]

Hi @lcatton! Thank you very much for confirming, and for sharing the output! I wonder why summary seems to be missing 🤔

Does the page still go fully blank after this?

[ebresie]

The ticket #26 is a jira issue which is I believe associated with the same thing.

The reference to Bit bucket in #26 was there was a similar ticket involving bit bucket which I believe is due to out of date api URIs in some context. For Jira and another api URI for bit bucket side

[lcatton]

@sdzh-atlassian Yes, the page is still blank. We are using the datacenter edition of the software if that makes any difference to the ticket fields available.

[stewartg]

@sdzh-atlassian,
Not sure if this helps but I'm seeing the same issue with pre release(3.3.24) and the release(3.2.1) versions. The Jira Issue pane contains a banner that says 'Something went wrong and Issue Does Not Exist' for any issue that I click on and doesn't display the issue at all and the dev tools error is 'viewIssueScreen.4da3df0f.chunk.js:1 Field error - no field when trying to render summary'. Happy to provide more detail if you think it would help.

[manuartero]

ey, came back from Christmas 🎄

do you need more info or traces @sdzh-atlassian ?

[SimeonBBorisov]

Hi, @sdzh-atlassian :)

As of Jira and Bitbucket (Atlassian Labs) version 3.2.2 I see this now instead of a blank page:

In reality the tickets do exist, however the extension can't load them correctly.

[manuartero]

Hi, @sdzh-atlassian :)

As of Jira and Bitbucket (Atlassian Labs) version 3.2.2 I see this now instead of a blank page:

In reality the tickets do exist, however the extension can't load them correctly.

this, same here!