You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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.
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.