Moving issue to different project with different workflow the issue still uses the old workflow

When we moved a JIRA issue to a different project and different workflow the moved issue still uses the old workflow. Is this working as designed?

Can the issue follow the moved projects workflow? JIRA 5.2.4.1

7 answers

Is it possible that, when you are importing the issue in to the new project, you are also setting the workflow through a predefined configuration file?

No it is not possible. When you move the issue to a different project , the moved issue will use the workflow which points to the new project.

I would recommend

-checking the workflow scheme that is associated with the source and destination project as it is highly likely that both projectsare using the same workflow scheme

 

Rahul

Issue types/screens/fields are different. Is that why?

0 vote

Hi Ken,

When you move an issue from one project to another one, it will follow the workflow of the new project. You say it follows the old workflow, could you please make sure both projects don't use the same workflow?

Some screenshots might be helpful as well, so we can understand which transitions you are seeing, and what are the available transitions in your workflow.

Cheers,

Clarissa.

Issue types/screens/fields are different. Is that why?

0 vote

No, it's not the issue types/screens/fields.

Have a good look at the "workflow scheme" for both the old and new project.  Are you absolutely certain that "bug" in project A is using workflow X, and workflow Y is used for "Bug" in project B, and that a moved issue is still using X despite being a bug in B?

Yes both are using default Agile Jira Integration workflow. Workflow scheme shared by 2 projects. Issue Type Bug scheme is different

If the workflow scheme is shared by the 2 projects, then there is no change of workflow and hence your question does not make sense any more. I'm afraid I really don't understand what the problem is now.

No configuration file used. I will change screen schemes and reindex

The screen schemes do not affect the workflow directly. You've also not clarified what the actual problem is. First you've told us that "the workflow does not change", then you've told us that "both projects use the same workflow scheme", which means the workflow SHOULD not change anyway. So there's no clear description of what the problem really is.

We changed the workflow to be the same since 1 wokflow was not Agile, so after the inital comment the issue changed. We then had to change all the issue type schemes,fields screens to one marked as Agile from the old workflow and setup

Ok, that makes a bit more sense now we know what you've done. But that also means the original question is answered, because the projects are now using the same workflow, and hence there is no "keep the old workflow" happening, it's the same workflow.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published May 21, 2018 in Jira Software

How large do you think Jira Software can grow?

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...

1,253 views 10 18
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you