nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do I automatically move an issue from one project to another?

Schuyler Bishop

We would like to find a way to automatically move issues from one project to another. For example: Issue status changes to "Approved" and issue automatically moves to a different project. Or, issue is reassigned which triggers issue being automatically moved to a different project, etc. There is no real criteria required except for the automation of issues moving from one project to another.

Is there any way to do this? Using a plugin, post functions...anything? Thanks in advance.

Accepted answers

All comments

Jobin Kuruvilla [Adaptavist]

You can certainly use a plugin but it is usually harder than you think. Each project can have its own workflows, field configurations, screens etc and the rules in target project (like a mandatory field) might prevent the move. And different workflows might require a workflow migration. And that is why JIRA doesn't offer it as a functionality (You have to use 'Move' which addresses all these concerns in different steps).

If the projects are identical, it is easier to do that in a plugin.

Schuyler Bishop

Hi Jobin, do you have a specific plugin in mind?

Jobin Kuruvilla [Adaptavist]

None that I can think of. I was suggesting about writing one!

Oliviu Nita

Hi,

I was searched for this and i was having a feeling that is not possible or easy... at least i have something to show to my bosses smile

I will not start to make the plugin, is beyond my capabilities...

Have a nice day

Maike Lorenz

Hi,

I have had the same issue and found a working solution for me.
So I like to share it .

We use "Automation for JIRA".
This is the tool that I use to solve this issue.
We use components in our projects. So we defined components to name different taget projects.
For example component: A => target project: "project A"
If a JIRA user sets the components of a ticket to "A", the ticket should be moved to "project A".

So I defined a automation rule with "Automation for JIRA":
If a ticket is changed and the new component if the ticket is "A", then clone the ticket to "project A" and delete it in this project.

This works fine for us !

Nachumi E

Hello, That's what i have tried but unfortunately the sub-tasks didnt clone to the new project,

My goal is to move the issue and its sub-tasks and comments to another project.

Is there a way to do it?

Nic Brough -Adaptavist-

That is a "clone and move new" action, not a "move issue". As such, it's

not an answer to the original question
not a move, clone does not clone the subtasks, only the parent

Joe Harmon_y3pgen

Maike, this is pretty close to what we want to try as well, but one thing I liked about the move option is that it kept the old key as searchable. That way the reference number was always there from the original project. Did you see the same issue?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

issue

jira

jira-administration

move