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.
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.
I achieved this mostly, but it is nowhere near as simple as just moving the ticket. The issue is what was referenced above, a move operation needs a lot of criteria from the agent to determine which fields should be kept/lost, etc. With different custom fields, you need a lot of values pre-set to tell JIRA or the plugin what to do with each issue.
I used Bob Swift's Create on transition to clone the ticket on the initial creation transition. This enabled me to run initial conditions checks on the issue to determine whether the issue needs to be "moved", then link the new issue to the original, as well as to pre-set all my custom fields so they would map correctly to the other project. This is not really moving the ticket, however, but creating a linked copy of the ticket in project you want the ticket moved to - this seems to be the only workable solution right now. Then, I used one of JWME's transitions to sync the linked issues' transitions, so that major workflow transitions would be set to the linked ticket as well. This is mainly so I wouldn't have to worry about one linked ticket being closed and another one floating around still open.
If you really want to get nuts, there's also a workflow toolbox plugin that will allow you to take the last comment of an issue and copy it to a linked issue, effectively allowing you to clone comments between issues. My main problem here was that you couldn't run this transition on both projects' workflows, as it would create a notification loop.
If someone could bring all these tools into one plugin, that would essentially allow ticket 'syncing' across projects, it would be a huge help. Because right now, to even get near a solution, you're talking about 3 or 4 plugins all working in tandem to bring one result that should be much easier than that.
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 :) !
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot