Strange Workflow Behaviour

[Nyenty, Tabe]

Hi there,

A customer approached me with strange behaviour within his Workflow. He configured a trigger that should transition when a Pull Request (Github) has been created. But the transition tab shows the transition name as "unknown" for some reason. Adding to that the status transitioned to itself whereas that step wasn´t configured. He had a global transition on the closed status.

So I assumed based on the following

that this might be the cause.

But he created a new Workflow without any global transition and the behaviour persists.

I am currently clueless as to what might be the cause. I have also reached out to Atlassian so far nothing promising from their end.

Does anyone has and idea, hint or solution?

Regards

Tabe

[Brant Schroeder]

@Nyenty, Tabe Is the client using normal workflow triggers delivered by Atlassian or do they have an app that they are using?

[Nyenty, Tabe]

Hi @Brant Schroeder ,

the client uses the workflow triggers delivered by Atlassian. We were able to make some progress on this issue.

1. We discovered that the data gets corrupted when a trigger is being added no matter the workflow (newly created or existing)
2. Atlassian Support is also in the loop, but there is no real solution to this.

Do you have an idea of how someone can get rid of corrupt data?

[Brant Schroeder]

@Nyenty, Tabe I do not, this is the first I have heard of something like this.  It will be interesting to hear more about what you receive back from Atlassian support.  Did they recognize it as a bug?