Automation that automatically tags delivery tickets

Question

Hey everyone 👋

I could use some advice on setting up an automation for our Jira instance 🙏

Context: We're using Jira Product Discovery to track our initiatives. Each initiative/idea in JPD is linked to delivery epic(s) in Jira Software. To aid reporting, we need to identify the delivery tickets associated with each initiative/idea, using a custom field.

What I am trying to achieve: I'm looking to set up an automation that is triggered when a delivery ticket is added to an idea in JPD. The automation should copy the summary of the idea ticket to a custom field on the delivery ticket.

Looking forward to hearing your suggestions. Thanks in advance for your help! 😊

Mirko

Mark Segall_iqztfr · Answer

The trigger is about the link which is project agnostic.  The easiest way to ensure that it only fires on the JPD project would be ensuring the project scope is set to multiple project and explicitly listing the two projects that are being linked (JPD and the other project).  Then you just need to be consistent in how the links are used (e.g. JPD is always linked to project x as the source or destination).  The link consistency will make your rule consistent.

Mirko Grahnert_p1eahn · Answer

Thanks @Mark Segall - is this the type of automation you would recommend?
Any suggestions on how to limit the scope of the automation, so that it is only triggered when the 'is implemented by' link is created from a ticket within our JPD project?

Mark Segall_iqztfr · Answer

Hi @Mirko Grahnert

The most important element of this is that you're using a link type that understand source/destination (e.g. Blocks/Is Blocked By, Clones/Is Cloned by) vs an ambiguous link type like "Relates To".  The Issue Linked trigger is very dependent upon the link type relationship.  This is further captured in the trigger description:

Rule executes when an issue is linked to another issue. {{issue}} will always refer to the source issue, so if ISSUE-A is blocked by ISSUE-B, this rule will execute on ISSUE-B. To access ISSUE-A, use {{destinationIssue}}, and to access the link type, use {{linkType}} (e.g. {{linkType}}

In its simplest form, the rule would look something like this (Note - I'm using the Blocked link type, but the premise is the same for any source/destination link structure)

* TRIGGER: Issue Linked (Blocked)
* ACTION: Edit Issue (Your Custom Field)* {{destinationIssue.summary}}

Assuming these two issues reside in separate projects, you'd need to make sure the project scope is set to multi-project or global which means the rule needs to be managed from System >> Global Automation (requires Jira Admin permission).