Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,969
Community Members
 
Community Events
176
Community Groups

Publishing workflow: : the current status of each issue needs to be changed so that it is compatible

Edited

 

I want to use a new workflow for bugs board.

I copied exisiting workflow and deleted 2 issues that we do not want to use anymore. The new workflow has been added to the workflows in the Project settings.

Now I am asked to associate status of two current issues (which I do not want to use anymore, therefore I edited the copy of a workflow) so that it is compatible with new workflows.

How can this be solved?

workflow.jpg

2 answers

1 vote

I am sorry, I do not understand the problem.

If you have removed some status from the workflow, then issues that are in that status can not have that status any more, because an issue has to be in a status in the workflow to show where it is in the process. 

When you migrate to the new workflow, Jira asks you what status (in the new workflow) is best to drop the issues into.  In your screenshot, your new workflow does not have "closed" or "(netgebruiken)", so it's asking you what issues in that status should be moved into.

I don't see what needs to be "solved" here?

I suspect your Workflow or Issue Type is shared with another project.  This happens when you "copy." 

Isolate your workflow by "copying" it, but then rename it.  For example if your workflow is called "Bug Workflow", name the copy "Bug Workflow for Project XXX." 

(The copied workflow will drop into the INACTIVE list, which is at the very bottom of the list of workflows.)

Go back to your Project settings, choose "Workflow", click on "Global Workflow Schemes", then add your new workflow "Bug Workflow for Project XXX" to the scheme. 

Return to your Project settings, choose "Workflow", see your new workflow in the list; and associate the new workflow with your issue type (Bug?). 

Now your workflow is only serving YOUR project, and should not request you to migrate status for other projects using the original workflow.   

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS

Atlassian Community Events