Is it possible to set up automation to move issue from one team-managed project to another project?

[Yuqun]

I'm currently setting up automation rule to manage three team-managed projects. one of the rules is based on the value of project 1 to move the issue to project 2. When setting the automation rule's action, I don't have Move Issue to Another Project option, only Move issue to board option. 

Is it possible to set up automation to move issue from one team-managed project to another project?

[Dave Mathijs · Accepted solution]

Hi @Yuqun Welcome to the Atlassian Community!

Good question, I don't find the Move issue in Issue actions either, now you get me wondering if it ever has been available in the past, don't think so.

When checking, I found the confirmation: The field with the id project and type project is not supported by Automation.

[Yuqun]

Thanks Dave for your quick reply and the warm welcome. 

I'm thinking if it is because the project is team-managed (as opposed to company-managed).

Please may I ask what 'The field with the id project and type project' means? thanks!

[Dave Mathijs]

I tried to reproduce with a company-managed project, but the same actions are available, also on a Premium Plan.

Well, it means that you cannot edit the value of the Project id/key or type of project, hence you cannot move issues from one project to another via automation, only manually with the move option.

[Yuqun]

Thanks Dave for confirming!

[Dave Mathijs]

@Yuqun Thanks to click the green 'Accept answer' button if my answer helped you.

[Bill Sheboy]

Hi @Yuqun -- Welcome to the Atlassian Community!

First thing, and without knowing the specific "why" you want to automate moving issues to another project, I recommend not doing this with an automation rule.  There is too much risk of an error / rule misuse causing a mess in your Jira site.  With that disclaimer out of the way...

There is a recently added REST API endpoint for bulk moving issues.  That could be used with the Send Web Request action to perform a move. 

Again, I advise against doing this, particularly because you also note using team-managed projects, and they are generally all configured differently, with unique issue and field types, and workflows, leading to mapping challenges.  This is a good reason why the UX "Move" feature exists: helping to interactively ask what is needed to perform a move successfully.

If you still want to try this, here are the references to get started:

• https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828
• https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-bulk-operations/#api-rest-api-3-bulk-issues-move-post

Kind regards,
Bill

[Yuqun]

Thanks Bill for your reply. We are currently setting up two team backlogs for them to work on different projects. There will be a central backlog to plan which tickets go to which team's backlog. We would not use this as a bulk movement, probably on the ticket-by-ticket base. I can move them manually, just thought it'd save some time if there is automation for this. But I can understand potential risk of having it fully automated.