You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
When I move to another project, Default status is "Cancelled" and then I have to change to "In progress" everyone. Can Admin change the default status for moving to this project ?
It's simply picking the first status it finds. You can't change it directly, from memory, it's based on the id of the status - first one it finds in the workflow gets used.
The step IDs correspond to the order in which the step itself was added to the workflow. In my case "Done" had the lowest ID in the workflow, so I deleted and re-added it, which resulted in it having the largest ID in the workflow. Hence, it appeared last in the list of possible statuses during the move issue wizard instead of first. So this is fixable, although it's a bit of a pain.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Mmm, not quite.
The step ids correspond to the order in which the steps were added. Globally though, not to each workflow. You could end up with your "fix" not working, if you've got more than one admin tinkering with workflows at the same time.
It's unlikely to happen, I am being pedantic, but I just wanted to note that it could still do unexpected things in some cases.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> Globally though, not to each workflow.
My experience doesn't exactly align with your statements. When I deleted and re-added a step from one workflow, then proceeded to another workflow, the latter workflow was unaffected by the change to the former workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.