Next available status transitions are not updating and requiring a page refresh

[Tamir Ganbaatar]

I got led to this explore community when trying to report a technical issue so here it is. When I transition a task in Jira to a new status, until recently, the behavior was that the next available status transitions would immediately be available in the dropdown. But now it's still showing me that the status I just transitioned to is the next one I can transition to - which is false and selecting it causes an error message. Image below shows that I marked the status to "In Progress" but the dropdown still shows me I can transition the status to "In Progress".

When I click the Start Progress transition again, I get a toast notification at the bottom of the screen like this:

Only after I fully refresh the page, do I see the correct and expected dropdown list. Jira didn't use to require refresh of the whole page until recently so I think this is a recent bug that was introduced.

[Andy Heinzer]

Hi @Tamir Ganbaatar 

I found a recent bug posted in https://jira.atlassian.com/browse/JSWCLOUD-26745

However it sounds like it hasn't been easy for users to reproduce here.  Could you clarify how you are reaching this particular issue?  For example, are you viewing the issue while on a board?  Or perhaps via a click through from a parent issue (like an epic)? Or more specifically, what is the specific URL in your browser when you can replicate this problem?

I have a feeling there might be another component/aspect here in regards to how Jira is loading and rendering the issue data.  If the workflow has constraints about which statuses can be called and when, then there might be other factors here that we would want to understand to be able to replicate this behavior.

Thanks

Andy

[Dave Rosenlund _Trundl_]

Welcome to the community, @Tamir Ganbaatar  👋

While it may be true that you have encountered a bug, I cannot reproduce these symptoms in my Jira Cloud instance. Therefore, I suspect some other change in your Jira config is causing this.

The most likely culprit is that someone has changed the workflow very recently ( I notice the wording is different now), and your browser cache still remembers the old names.

Have you spoken with your Jira administrator about the issue you are seeing? Or, if it's a team-managed project, the project administrator?

If you still think you're encountering a bug and something is wrong with Jira, the community may not be the best place to resolve this. You'd have to open a support ticket with Atlassian.

I hope this helps,

-dave

[Tamir Ganbaatar]

Hey Dave, right after I posted this, I went back to reproduce the issue and it didn't reproduce for me. I tried multiple refreshes and the problem was fine. I checked with some of the other members of my team and they reported still seeing these issues, and when I got back to reproduce it a few minutes later it reproduced again. So my hunch is that it's sporadic and not 100% reproducible. And I just posed a screenshot from my developer console https://community.atlassian.com/t5/Jira-questions/Re-Next-available-status-transitions-are-not-updating-an/qaq-p/2733638/comment-id/1027948#M1027948 which shows that the page is loading some deprecated js. I emptied cache and did a hard reload but still saw this error. Maybe this deprecated JS is causing sporadic issues on the page?

[Tamir Ganbaatar]

In the dev console, I see this warning log about "dropdown constructor" which maybe related?

[Dave Rosenlund _Trundl_]

Well, that changes things! I suppose it could be related.  Rather than opening a support ticket (as I previously suggested) let me ask someone from Atlassian to have a look at this thread.

Stay tuned.

-dave

[Daryl Marsh]

Could be browser issue. Does it happen if using another browser?