Automation rule for getting update on Cloned issue to different project

[Sohail Alam]

This is rule I created. All I want is when the clone ticket ABC (Cloned) is moved from Project A  to Project B and if ABC (Cloned) is updated to Done how can I update the ticket ABC (Original) in Project A. This is the automation process I am using

[Bill Sheboy]

Hi @Sohail Alam 

For a question like this, please also post an image of the audit log details showing the rule execution, and explain what is not working as you expect with the rule.

Until we know that...

What is the scope of your rule: project, multi-project, or global?

A project-scope rule can create (or clone) issues into another project, but it cannot access or edit them.  To do that, the rule scope must be multi-project or global. 

Please discuss this rule with your Jira site admin in that case as only site (or org) admins can manage those rules.

Kind regards,
Bill

[Sohail Alam]

So for this one, there was No change in Audit log, and our scope would be Global.

Help is highly appreciated

[Bill Sheboy]

I still do not understand: what is not working as you expected with the rule?

Knowing that will help the community to offer better suggestions.  Thanks!

[Sohail Alam]

when the clone ticket (ABC -Cloned)is moved from Project A  to Project B and if (ABC Cloned) is updated to Done in Project B , the original ticket status in Project A remains the same i.e To-Do. 

What I am looking for is, (ABC - Cloned) status is marked as Done in Project B then (ABC - Original) in Project A should also be Done.

Thanks

[Bill Sheboy]

That seems to indicate your rule may not be triggering.

Please post an image of the audit log details for your rule.  That will confirm if the rule is triggering, and which rule steps are processing.

Also, I strongly encourage you to not make this a global rule unless you want this behavior for all of your projects.  Instead, consider making this a multiple-project scope rule instead.

[Sohail Alam]

[Bill Sheboy]

That audit log entry shows issues only in one project.  Were you expecting them to be in different projects?

[Sohail Alam]

Yes, Project A and B

[Bill Sheboy]

Where / how did you clone the issue into another project: manually using the UI, with an automation rule, etc.?

Perhaps when the issue was cloned it was not put in the other project...Or, there are multiple cloned / linked issues, and this rule's scope cannot see the ones in other projects.  (Please re-read what I noted earlier about rule scope.)

[Sohail Alam]

Cloning was done manually and then manually moved to different project.

[Bill Sheboy]

Please examine the issues involved (the original one and the cloned one moved to the other project) to confirm the links still exist in the issues.

For the audit log you show, the issues do not appear to be linked.

To confirm your rule scope, please post an image of your rule details at the top.  This is the section showing the rule name and scope.