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
I setup a team-managed JWM project (using the project management template).
The JWM project has some items that I'm selling. It's pretty basic.
I changed the "Task" issue type to "Sale." I added custom fields for that Issue Type. Everything good!
I then edited the workflow, and added three new status':
Then I deleted the "In Progress" and "Done" statuses.
When I go return my board, I see all six columns (including the "In Progress" and "Done"), even though there are only four present in the workflow.
I tried to get around this by deleting the new status' from the workflow - however when I delete them from the workflow, they still exist even though they are present on the workflow - and subsequently, now I have *every* status represented as a column in the project board and can't find anyway to delete them.
If I go back to the workflow and edit it, then go to add a new status, I see that the old status' which are no longer in the workflow are still present as part of the project, even though they aren't part of the workflow.
I was going to migrate the issues over to a new project and start over - however I believe all the custom field data will be lost in the process.
Kind of a nightmare. Any suggestions?
Hi Nathan,
This appears to be a bug as I can reproduce the same results. You should report this to Atlassian here:
My guess is, you need to replace the workflow scheme (just like you would for any Company Managed project).
Make sense?
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.