JIRA Status doesn't update after approval unless reload

[Victor DeVore]

Hello,

This is a recent issue that popped up.  When I have a ticket/issue that is transitioned to a new status after it's been approved, the transitions for the status updates correctly, but when I click on the status button it still shows the transitions from the previous status.

The transition doesn't update unless the user reloads/refreshes the page.

Before reload:

After reload:

The transitions from the previous screenshot should display under a different status.

[Fahad Siddiqui]

@Victor DeVore check the workflow of the issue, there is some validators or conditions.

[Victor DeVore]

Hi Fahad,

I checked that, there's only one condition and it's this one:

A few things I noticed:

1) It only happens for statuses that have an approval step (approval is set, it's based on a single user custom field)

2) It does correctly show the right transitions after I refresh the page.

3) Other transitions behave normally as expected.

I haven't made any changes to the workflow, nor have I installed or changed any plugins... this seems to have occurred within the past week.  This was working perfectly before, but I've been getting reports of this recently and I'm stumped as to what might be causing it.  The status does update and transitions do show correctly, but after I refresh the page (F5).

[Fahad Siddiqui]

@Victor DeVore do full re-indexing and then see. may be this will fix your issue.

[Victor DeVore]

Hi @Fahad Siddiqui 

I don't believe I can do a full re-indexing since I'm using Service Desk Cloud version.

[Victor DeVore]

Hi just a quick update.  I submitted this as a bug too.

This happens with any status that has an approval step.  So when a status is approved, the status text changes to the next step in the workflow, but the transitions that display do not match the new status.  A refresh/reload of the page needs to occur for this to happen.

[Victor DeVore]

Hi All,

Just an update, Atlassian confirmed this is a bug.  For those also experiencing this they referenced two existing bugs:

https://jira.atlassian.com/browse/JRACLOUD-75145

https://jira.atlassian.com/browse/JRACLOUD-71849

You can refresh the page or turn off the new Jira issue view as a workaround.