Different descriptions being shown to myself and colleagues

[Alan Henderson]

I am sitting with my colleague looking at the same ticket(s) on our JIRA board experiencing some very strange behaviour.

Sometimes the description is empty on her screen but fine on mine, other times it's reversed.  When it's empty, clicking on it sometimes displays the actual description, other times it remains blank.

Sometimes the description matches on my screen vs theirs, other times it shows something different (e.g. from a different ticket).

When we are viewing an incorrect description and if we click to edit, it will show the correct description. Other times when it's showing the correct description, editing it will show an incorrect description.

In all of these cases, if I were to save it would overwrite the actual descriptions which is clearly dangerous. 

Cache cleared, logged-in, logged-out, reboot... several steps taken.

[James Gamble]

Hola Alan,

Because the description sometimes shows content from another work item, and the edit view can also load the wrong content, I’d stop editing or saving affected descriptions for now. This sounds more serious than a typical browser cache or screen configuration issue, as there’s a risk of overwriting valid data.

As a quick isolation test, try opening the same affected work item directly from its full URL in a private browser window with all extensions disabled. It’d also be useful to test from a different supported browser and, if possible, a different network. If the problem persists, it strongly suggests it isn’t local browser data.

I’d also compare what Jira returns through the REST API with what the browser displays. A Jira admin can open https://your-site.atlassian.net/rest/api/3/issue/ISSUE-KEY?fields=description after replacing the site and work item key. Don’t post the output publicly if the description contains sensitive information. If the API consistently returns the correct description while the interface displays another work item’s content, that would point to a rendering or client-side issue rather than the stored field value.

Since you’re on Jira Cloud Premium and have already completed the basic cache and session troubleshooting, I’d raise this with Atlassian Support as a potential data-integrity issue. Include the affected work item keys, timestamps, both users’ browsers and versions, a screen recording, and whether the REST API returned the correct content. Avoid including sensitive description text unless Support requests it through the case.

Thanks,

James

[Laura Pellizzari]

I suggest to directly copy paste your question in ROVO and look for suggestions

ciao

Laura