How do automate the change of a status of a primary ticket when the clone is changed in diff project

[Claire Smith]

I'm using automation to create a clone in a different project to address the ticket in the originating project. I then want to reflect changes in the clone ticket back to the primary ticket such as comments and status. I've tried using branching but can't get it to work.

[Ste Wright · Accepted solution]

Hi @Claire Smith 

This is possible as long as the tickets are linked together

I assume they are after they were cloned, using the link type "clones / is cloned by"?

If yes, see some example rules below!

---

Note: If these rules are pertaining to multiple Projects, you will need to use a Global Automation Rule. You can access these via...

• Settings (cog icon in top-right)
• System
• Global Automation (from the left-hand menu)

---

Copy Status

This is assuming the statuses are the same between the originating and cloned issues - if not, there's other options (eg. if status A changed, set status B).

• Trigger: Issue Transitioned
• Condition: Related Issues Condition
  • Related Issues = Linked Issues
  • Link Types = clones
  • Condition = Are Present
• Branch: Related Issues
  • Type = Linked Issues
  • Link Type = clones
    • Branch-Action: Transition Issue
      • Destination Status = Copy from trigger issue

---

Copy Comment

As far as I know, you can't "duplicate" a comment between issues - i.e make the same comment from the same author - but you can copy the comment's details.

• Trigger: Issue Commented
• Condition: Related Issues Condition
  • Related Issues = Linked Issues
  • Link Types = clones
  • Condition = Are Present
• Branch: Related Issues
  • Type = Linked Issues
    • Branch-Action: Comment on Issue
      • Comment...
        • Use smart values to populate comment information, such as...
          • Author's name - {{triggerissue.comments.last.author.displayName}}
          • Comment body - {{triggerissue.comments.last.body}}
          • ...etc

---

Let us know if this helps!

Ste

[Claire Smith]

Amazing!! I wasn't using a global rule even though I thought I had!! So I was able to change the scope in the global admin.

Now to create lots more fun automation!!!!!

[Ste Wright]

Awesome, glad it works!

If this answer helped resolve your query, could you accept it? That lets others know it can help them too :)

Ste

[Claire Smith]

Do I need to have separate rules for different triggers? Or can I create a rule that has 'this trigger or this trigger' but they have different actions for each trigger?

[Claire Smith]

Or shall I post that as a new question?

[Ste Wright]

Hi @Claire Smith 

I can answer it here :)

Unfortunately you can't provide multiple triggers for the one rule, aside from the trigger "Multiple Issue Events" - which can be triggered based on one or multiple events, including issue...

• Created
• Updated
• Assigned
• Transitioned
• Moved
• Deleted

You can have multiple actions from one trigger though - eg. if an issue is transitioned, copy the Status and copy the last comment.

Ste

[Claire Smith]

Thanks - I've used the multiple actions which is useful.....just hoping to keep the number of global rules down for each trigger - I want to use the 'transitioned' trigger twice so  with different 'status' triggering different 'action'

Cheers!

[Bill Sheboy]

Hi @Claire Smith 

Adding to Stephen's answer...

You appear to be using a Standard license for Jira Cloud.  Is that correct?

If so, please note there are limits for global / multi-project rule executions per month, as explained below.  And your rules seem to use very simple triggers, and so could trigger quite often and rapidly consume your monthly limits.

https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/

Kind regards,
Bill

[Claire Smith]

Thanks Bill - I've restricted the rule trigger to my single project within the global rule so hoping that it won't create too many executions as we have very few tickets coming through the project. I will keep an eye on it though!

[Bill Sheboy]

Sounds good, and my understanding is...

• Rules defined at a global scope are counted against the limit, even if they only impact one project.
• Rules defined at a project scope do not.

I am trying to find out if the "Service Limits Breached" trigger can detect this.  If it does, it may be helpful to have a global rule with that trigger which emails you when the limit is approaching / breached.  Then you can take appropriate actions.