The admin who built the workflow has added (2) to the end of the transition names for some reason. Best guess is that the workflow already had transitions with those names, which blocks duplication, so the admin added the extra text to distinguish them from the originals (stretching the guesswork - they probably got rid of the old transitions as well, so the (2) should have been temporary and removed later)
I can't remember if it's automatic when you reuse an existing transition name, so it might not be a totally human action. However, the other possibility is an addon doing odd things to the names. Could you nip into the workflow and click on the transitions to see what their actual names are? In fact, it would be easier (especially if you are going to show us) to use the text view of the list of status - that tells us more in one go than the diagrams.
We wanted the workflow to allow all statuses to transition freely to other statuses so we setup the workflow as seen in the attached diagram using the "All" option. Could that be the issue? Do we actually have to setup transitions between each status to the others?workflow.jpg
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
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