How do I configure a workflow in order that....

Question

How do I configure a workflow such that:

An issue in PROJECT-A has a status of DONE

The issue needs to be moved to PROJECT-B

On moving it to PROJECT-B it picks up a status of NEW

I am testing this on a jira instance that has two projects, A and B. A is scrum, B is Kanban. I have no custom workflows in either project.

The option to set a new status when using the "MOVE" option on the issue tells me that "Step 2 is not required"

This is the step where I believe  I should be able to set a new status.

Is this because "Done" is a special status in Jira or do I need to make some customizations to allow me to achieve this?

Nic Brough -Adaptavist- · Answer

Nope, didn't see the follow-up before I wrote the last answer.  Repairing a mess is a good reason to move things though, with the eventual aim of shutting down A.

I think having slightly different workflows is the only real answer here.

Edward Moore_3f4rup · Answer

Ok thanks for that Nic. So the trick here is to ensure that there is no overlap in the names of the statuses between the two projects forcing Jira to ask me which of the statuses I want it to land in when it arrives in the second project.

I don't know if you had the opportunity to read my second post explaining the situation in a bit more detail before you replied but the situation here is pretty much "Project A is borked from a setup and config point of view, we need to move to project B however there is a lot that remains to be done in project A and much of that work is being done by a third party"

This is absolutely a rescue operation. Project B needs to be owned and managed by the company I am with, and account for all the internal processes and integrations. Project A is largely under the control of the supplier.

Nic Brough -Adaptavist- · Answer

>The issue needs to be moved to PROJECT-B

This is usually a broken process in Jira terms.  Issues should generally not move between projects.  When they do, it should be because you're doing things like closing an old project but keeping some stuff open, or because a mistake was made and the issue went into the wrong project when created.

Moving an issue is hard work.  You have to do all of the work around checking the config between source and target is valid, then move it, feeding it with any missing or changed information.

When you use the UI to do this, it simplifies it as much as possible, and only asks you about things that are necessary.  If you have the current status in the target project, it won't ask you about it because it assumes you need the same.

So, two points here.

* If you continue to do this, you could edit the workflows, such that there is little or no overlap in status in the two projects.  E.g. in project A, have To-do, In-progress, Done, and in project B, use New, Doing, Ended.  Then if you move from A to B, Jira will have to ask which status the issue should land in.
* Ideally, review your process and redesign it, getting rid of the idea of moving between projects.