Can you create an action to move issue to another project

[Hardeek Patel]

Want to create this automation- 

1. When issue is created containing text in summary

2. Move to another project

3. Edit fields in project

4. Assign to person

I know I can this do if I remove step 2 and make the automation within the same project, but can't figure out how to change the project, assign it and hopefully edit the status fields (different from current project) in the desintaiton project.

[Mark Segall · Accepted solution]

Hi @Hardeek Patel and welcome to the community!

Jira is not designed for routinely moving issues from one project to another and that's because there is a lot involved behind the scenes.  Jira has no way of knowing that the target project is configured the same (statuses, issue types, field configurations, etc.)

So, it is best practice to instead clone or create issues onto other projects.  You could extend your automation a bit to make a clone, link it to the source issue, and then close out the source issue as a potential workaround.

[Bill Sheboy]

Hi @Hardeek Patel -- Welcome to the Atlassian Community!

Yes, and...to Mark's answer:

There are a couple of suggestions to add a "move action" for automation, which you may review below.  Move is not supported in the REST API and there are quite a few possible problems, requiring human interaction, and so it probably would not get implemented.

https://codebarrel.atlassian.net/browse/AUT-41
https://jira.atlassian.com/browse/JSWCLOUD-22679

Kind regards,
Bill

[Hardeek Patel]

Thanks Mark and Bill.  I figured there might be some restrictions around it,  like you said due to not knowing the configurations of the target project.

Thanks for the links Bill, I'll check those out and play a little.