Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
minLevel1
maxLevel3
outlinefalse
typelist
printablefalse

Advanced Links in Jira Cloud are often assigned custom field properties and functionality which are not exact. Thus, common distinct from Advanced Links in the app’s Data Center version, where they are built as Jira's standard custom fields. As a result, some of the typical automation field-based triggers and actions are not as accessible in Cloud as they are in DC. However, there are a few ways of using Jira automation rules:

  • using a webhook URL to trigger the automation

  • manage links by setting entity property

Trigger automation rule with link update (via webhook URL)

Triggering automation through Advanced Links is possible through any of these events:

  • the issue is linked via an Advanced Link Panel

  • the issue is removed from the Advanced Link panel

To begin, you need to obtain the webhook URL that will be used to trigger Jira automation:

  1. Navigate to the automation configuration page (global or project-level)

  2. Create a new rule: click on the "Create rule" button to start creating a new automation rule.

  3. Select the trigger: under ‘Integrations’ see and select the ‘Incoming webhook’ trigger.

  4. Copy the webhook URL.

Then, keep the automation tab open, open a new one and navigate to an Advanced Link configuration page. Open the link ‘Actions’ menu and select ‘Manage automation’:

...

Click the ‘Select Rule’ button. Give the automation a name and select the trigger. There are two options to select from:

  • Issue linked: the rule is triggered when the issue is linked via this Advanced Link.

  • Issue linked deleted: the rule is triggered when the an issue linked via this Advanced Link.

Then, insert the webhook copied from the automation configuration page and click ‘Create’. Then close the automation dialogue.

...

Go back to the previous page with the automation rule. Continue editing the rule by adding a new action, or condition or creating a branch. After configuring the rule, be sure to save and activate it.

That's it! You have now configured the automation feature to trigger Jira automation using a webhook URL 👏

Set Entity Property

Advanced Links in Jira Cloud are distinct from Advanced Links in the app’s Data Center version, where they are built as Jira's standard custom fields. As a result, some of the typical Automation field-based triggers and actions are not applicablecompatible with them. However, storing data in issue properties enables Advanced Links to be used we can utilize issue properties to store data, allowing us to use Advanced Links with a Jira Automation action called Set Entity Property. By using incorporating smart values it enables us to add , we can append key/value pairs to an issue or , in our case, add new links to our Advanced Link field.

  1. Go to Automation RulesCreate rule.

  2. Select and configure trigger requirements → Save.

  3. Select New componentNew action → Set entity property.

  4. Select “Issue” in the Entity type field.

  5. Enter Advanced Link description according to the example:
    assetlink_inward_4942, where:
    assetlink_ is a fixed value
    inward_ is the direction of the Advanced Link field to which it is required to link new relations
    4942 is the Advanced Link field’s ID number. To see the ID number go to Manage AppsAdvanced Links. Hover over the Advanced Link → find a URL in the lower left corner of the page with an ID number e.g. https://apps.stagil.com/sajc/relation/4942/outward

  6. Enter Property value.

    1. To add more Advanced Links to the existing use:

      Code Block
      {
      "add": ["EIP-3", "EIP-4"]
      }
    2. To set new Advanced Links instead of existing use:

      Code Block
      {
      "set": ["EIP-3", "EIP-4"]
      }
    3. To link issues that are mentioned in the comment by issue key use

      Code Block
      {
      "add": ["{{comment.body}}"]
      }

      It is important to make sure that the issue key remains in the text format. If the issue key is saved as an issue link, the automation rule will not be triggered.

...