Hi everyone, I am new to jira please help me with this issue. After creating a project and an issue, while viewing the issue it is showing in progress(2), to do (2). What does those numbers (2) imply and how to remove it?
The number for status and transition is an identifier. The reason is that there may be several transitions, for example, that have the same name but are used in different workflows.
When you see a selection list with multiple transitions with the same name it helps you to choose the correct one by id.
You cannot remove and should not remove them. They are there for a good reason.
That doesn't make sense, I don't understand it. A transition can have properties, but what does "specified in (2)" mean? Where's this (2) you attach properties to? And, again, transitions do not appear in issue panels, so I don't know what you are looking at.
Does your workflow have duplicate transition names then? What you see in the history is the change of status, and the status IDs are added to the string (because it's possible to change or delete status, so the history is trying to preserve the full history without referring to stuff that you've changed), nothing to do with transition.
i changed the transition names in workflow to different number, after that when i went to transition options, the prev transitions havent been changed, whereas the change is reflecting in workflow. I dont know how to check whether a duplicate workflow exist . please help me out here
It's unique for that particular workflow step. So for example, your "Bug Workflow" can have 2 transitions named "In Progress (1)" and "In Progress (2)". If you made changes to "In Progress (1)" like added validators, postfunctions, it will only affect that transition. So, if you re-use transitions with the same ID, your changes to that transition will apply to all. The same scenario has their merits.
You cannot remove it.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
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