Browser page refreshes after issues are opened

[Alex Tsekenis]

This issue relates to Jira Software cloud. It is experienced by multiple users in the company. 

In the kanban board view, when we click on an issue to open the issue view, after a few seconds the page is whole page is refreshed. This is frustrating, wastes time and can lead to erroneous selections.

[Michel Neeser]

Hi @Alex Tsekenis

This sounds like a browser issue. Are you all using the same browser in the same version? Is the issue persisting if you completely restart the browser? Do you experience this behaviour on every issue or just on specific ones?

[Alex Tsekenis]

Hi @Michel Neeser , the issue is reproducible on:

• Safari 17.1
• Chrome 119.0.6045.160
• MS Edge 119.0.2151.72

Tested on multiple machines.

It seems to be for all issues, but not always. Tested on a kanban and business projects.
It felt that it was only happening for issues with larger/more attachments, but this is not the case.

The issue tend to happen more often when the page is "waiting on <domain>.atlassian.net" for a few seconds, which is often (but not always, or so it seems) followed by "waiting for data.pendo.io".

[Michel Neeser]

@Alex Tsekenis

The fact that you have to wait a few seconds for the page to load, and that the issue is reproducible on multiple machines makes me think of a networking issue. This may explain the reload of the page after opening an issue.

Are you using a VPN or a special network configuration? Is the issue persisting if you try it in another network, for example from your home network?

[Alex Tsekenis]

@Michel Neeser To answer your questions, the issue is reproducible over different networks/configs, including home networks. Also, to clarify what I said in the previous comment, the issue view page has already fully loaded before the page refresh happens, without user prompt.

The good news is that for the last day we seem to not have the issue anymore, no changes made on our side. Speaking with staff, one of them has experienced the issue before working at a multinational defence company, and they resolved it in a couple of days by contacting Atlassian. I am still not sure what the issue is/was or how it was resolved for them, but everything is pointing to something on the Atlassian side.

We will monitor the issue in the next few days and if it happens again I will see to contact someone at that other company to find out what was causing it for them and will post any info here.

[Michel Neeser]

@Alex Tsekenis Thanks for the update. Alternatively, you can contact Atlassian Support directly. They probably already know about this issue if the company you mentioned has resolved it by contacting Atlassian.