Automation not triggering for cloned or moved issues

Question

Hi,

I have an automation running in a specific project where a custom field (SLA) is added whenever an issue of a certain type is created. There are instances where the issue is created in another project and is cloned/moved into this project. In these cases, automation is not triggered. What is the best way to handle this?

The screenshot shows the automation trigger.

Peter Nixon_c2ypwv · Answer

Did you ever sort this out? I am having a similar issue where if a ticket is created directly in our service desk then the automation works, however when a ticket is created from cloning the automation doesn't work.

Possibly it is to do with how the field is populated. When we create it directly, it comes from a Smart Form. But when it is cloned it comes direct from the original ticket so possibly doesn't register it as a Value Change for the field.

Bill Sheboy · Answer

Hi @Athira Krishnan

You would need multiple rules with different triggers to do what you asked:

* issue created -- to handle issue creation or cloning
* issue moved -- to handle issues moved from another project

Kind regards,
Bill

Kumar_rajarapu · Answer

Hi @Athira Krishnan ,

Created Automation rule Based on Field value change, it would be user picker or any other field, issue should be clone to different project.

below link will be helpful to you to create Automation rule:

https://community.atlassian.com/t5/Jira-questions/Automation-clone-issue-and-move-to-different-project/qaq-p/1975729

Regards,

kumar