Automate Issue Creation Across Jira Data Center Instances

Summary

This article will help you automate Issue Creation from one Jira instance to another using a rule.

Solution

You need to have two Jira instances configured to use this rule.

Configure rules on Automation for Jira in both instances:

• Automation for Jira must be installed on both instances, sending the webhook from the Source Jira instance and receiving the webhook on the destination Jira instance.

• Create/identify the project on both Jira instances in order to receive the work items created dynamically.

• Create two rules, one for the sending webhook from the source instance and one for the receiving webhook on the destination instance.

Tips for implementation:

• Start both rule creations at the same time, so you can easily copy and paste the value of the Webhook URL

• Start implementing this with only the summary and description fields. Improve by searching for the fields one by one.

• You can add an action: Log action on the rule in order to understand what is inside the webhookData smart value. It helps in figuring out the pattern that is needed to follow to retrieve the fields as we wanted.

Detailed Steps using Example

Here's an example of how the rule can be configured in order to make it work:

Rule for Jira Source instance

• Create a rule to send the webhook to the Jira Destination instance.

• The rule has the components

  • Trigger: Work Item Created

  • Action: Log action (optional)

  • Action: Send web request

• Details on the Send web request action:

  • Webhook URL: This URL is retrieved when creating the rule on the destination Jira instance

  • Headers (optional): This is an optional setting and can be used based on requirements.

  • HTTP method: It is POST because you're sending information to the webhook URL.

  • Webhook body: To make things simpler, select Custom Data. You send all the required issue data using Smart values, which are placeholders for dynamic content.

    custom data

    1 2 3 4 { "summary": "{{issue.summary}}", "description": "{{issue.description}}" }

Rule for Jira Destination instance:

• Create to receive the webhook from the Jira source instance.

• The rule has the components

  • Trigger: Incoming Webhook

  • Action: Log action (optional)

  • Action: Create a new task

Trigger: Incoming Webhook

• Webhook URL: To direct the data towards this application, we'll need to use this URL in the Webhook URL field of the previous rule. Copy and paste it carefully into the rule of the source instance.

• Execute this automation rule with: Select Issues provided by webhook HTTP POST body, as we are sending the issues directly through the POST body.

If you have selected Custom Data in the rule configuration of the source Jira instance, the above option can be used. Otherwise, you can select No Issues from the Webhook.

Action: Create a new issue

• Project: Select the project under your Jira instance that must receive all the issues

• Issue Type: Select the issue type that the issue will be created on.

  • If you need several work item types, you can add some conditions with an If block condition and create separate Create Issue actions for each type of issue.

• Summary and Description :

  • Use a Smart value that works as a way of retrieving data that came from the Webhook data.

    • The webhookData object contains the fields object with all the fields..

    • For the summary, use {{webhookData.fields.summary}}

    • For the description, use {{webhookData.fields.description}}

    • Add all the fields you want under the Choose fields to set option

    • Use the same logic to get the field values from the webhookData object.