Record of Transitions Missing within "Transition Tab" in some issues

Nyenty_ Tabe February 29, 2024

In some issues, transitions through a workflow are not being recorded in the "Transitions" tab of the issues, preventing queries from working properly. 

Has anyone faced this issue before and has a reason as well as a solution for it?

 

Regards

Tabe

1 answer

0 votes
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 29, 2024

Can you provide detailed example? Is there anything unique about the transitions in the workflow?

Nyenty_ Tabe February 29, 2024

Hi @Jack Brickey there is nothing unique about the WF.

The following example is from a triggered status transition towards Github. "In PR Review" should be appearing.

Transition.png

It happens randomly across the Project. A Re-Indexing did not work

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 29, 2024

I have never observed this. I will cast a net to colleagues.

Nyenty_ Tabe March 6, 2024

Hi @Jack Brickey

an additional update from my side.

The issue seems to come when the set trigger on the Jira side is been fired at the same time the corresponding event is taking place. I.E. Pull Request created, merged etc.

The Trigger seems to make a jump while transitioning (see second pic. There´s no such transition in the WF).

Below attached are the history, transition tab, the set trigger the workflow and the transition in which the trigger is been placed.

I´m not sure what is going on here. Is it Jira or Github-related?

 

Kind regards,

Tabe

History_T.pngTransition Tab.pngTrigger PRm.pngWF.png

 

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 6, 2024

Unsure TBH but it does strike me as a race condition sort of side effect. I would suggest reaching out to Atlassian Support.

Nyenty_ Tabe April 3, 2024

Hi @Jack Brickey ,

I think I found the cause and the solution. The customer had a trigger configured and a global transition. Both are prone to confusion as mentioned by Atlassian.Trigger Error.png

All affected workflows happen to have a global transition.  Removing the global transition will let the trigger work as intended.

Thanks for your Support.

Like Jack Brickey likes this

Suggest an answer

Log in or Sign up to answer