How to move issues automatically after closing a sprint

[AlainD]

Hello,

We are using a multi projects workflow in our team, where we move a issue from one project to the other in its life cycle.

Let's simplify it by saying that there is a projectA where the issues are analysed and defined (by analysts) during one sprint, then the issues Done in this project (ie fully analysed and ready for development) are moved at the end of the sprint to the projectD to be ready for the dev team to handle over the implementation.

Is there a simple way to automatically move the issues in status Done from projectA to the backlog of projectD when an analyst of projectA closes the sprint ?

I am aware of the post function of workflow transitions for the issues but I don't know how to react to a close sprint event if such event exists at all in Jira, and how to automate this task. I would appreciate to receive some advices please.

Thank you.

We are still running a version of Jira Software for information.

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

Moving an issue in Jira is a structural thing, because the project and issue type define how an issue is configured.  

So it should not be done as part of a standard process.  Move is for housekeeping, migration, redesigning the way you all work, and the occasional genuine "sorry, put that in the wrong project" accident.

Because of this, no, there is no "easy" way to move issues, nor are there built-in automations or functions for it.  You have to manually look at each one, go through all the checks for incompatible settings and tell Jira the minimum to change on the issue to make it match the new shape of the issue.

You should really take a look at the issue lifecycle you have - they should really not need to move between projects.  I would keep them in the same project, with a workflow that has phases for analysis and development, and then have very different boards for the analysers and developers to work off (briefly, the analysers boards "done" column would be the developer's "to do" column)

[AlainD]

Thank you very much for providing such great details, they are very valuable for understanding the philosophy of Jira and how maybe our teams should consider changing our workflow in order to do things the "right way".