When we create a new workflow, the default initial status is Open. But we changed that to "Pending" and we also have "Open" in the next/following step. It gets saved correctly and we are also to test it. But after a few minutes the statuses are exchanged. The "Pending" changes to "Open" (initial status) and vice versa. We have no idea why this happens. We want to have our initial status as Pending for all workflows for this particualr project. Any suggections/answers please.
Thank you for the reply. No there is nothing like that. It happens automatically to the workflow. It's not someone chaging the status, but the actual workflow changes (Pending changes to open and vice versa) automatically. Even when we change it back again, it reverts back :(
Right, that doesn't happen without an administrator changing something.
I need to be exactly clear about what you are seeing here, and I am imagining two different scenarios. I'll just repeat back my understanding so you can tell me if I have misunderstood:
Is it either of those?
The Jira administrator is building these new workflows. Scenario 1 is exactly what happens. The work flow is : Create Issue --> Pending (Initial status) --> Impact Analysis --> Approve --> Open. But after a few minutes both statuses get swtiched in the workflow & when creating a new issue as well. Scenario 2 doesn't apply as all our workflows have both these statuses.
Also adding to Scenario 1:
5. The Open status changes to Pending
Hope this helps
Ok, can we expand on "switched"? (Sorry, bear with me here, I'm going through all sorts of odd scenarios in my head)
You're looking at the workflow diagram which shows: Create Issue --> Pending (Initial status) --> Impact Analysis --> Approve --> Open. Then, half an hour later, the diagram is exactly the same, EXCEPT that the status names are now showing: Create Issue --> Open (Initial status) --> Impact Analysis --> Approve --> Pending
Could you check one quick thing for me - the "last edit" time (and user) on the workflow that has changed? Is it when the workflow was created, or when the "swap" happened?
I have a sneaking doubt I know exactly what is happening, but need to know about the time stamp to check it.
It's one of your other administrators, or possibly even you when you go into another workflow.
The status "open" and "pending" are being renamed. The workflow isn't changeing, it draws the names from a global list. Which is being changed. My best guess is that you're fiddling with the status when you're creating your workflow, and it's upsetting someone elses workflow. So when they see their workflow break, they're changing them back. As I said, it might even be yourself, trying to correct two workflows!
I can confirm none of the other adminstrators change it. But I can say one thing. Whenever it switches, we rename "Pending" to something like "Pending2" and then rename "Open" to "Pending" and again "Pending2" to "Open" Is this what messes up. If so, how do we fix it. Please advise
That is exactly the problem. Stop renaming the status. They are GLOBAL - you change the name, it's going to change in EVERY WORKFLOW.
If you're pointing a create transition to the wrong status in a workflow, renaming the status is completely the wrong thing to do, you must change the endpoint of the transition.
Just mark the original answer as correct - same effect and people will be able to follow the thread if they have the same issue!
That was a very interesting investigation by the way - I had all sorts of weird ideas about what it might be, and it was entertaining ruling them out until my brain went "aha!"
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs