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

KP11
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 7, 2015

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

1 vote
Andrei RIPA May 7, 2015

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?

0 votes
KP11
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 8, 2015

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

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 8, 2015

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.

KP11
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 8, 2015

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

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 10, 2015

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.

0 votes
KP11
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 7, 2015

image2015-5-7 11:34:24.png

0 votes
KP11
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 7, 2015

image2015-5-7 11:33:49.png

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 7, 2015

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?

KP11
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 7, 2015

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

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 7, 2015

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.

0 votes
cgauterio
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 7, 2015

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.

KP11
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 7, 2015

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

0 votes
Rahul Aich [Nagra]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 7, 2015

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

KP11
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 7, 2015

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

Suggest an answer

Log in or Sign up to answer