Jira Automation

See Automated Clone for all Deep Clone automation use cases.

Presets

Create at least 1 preset with your preferred clone settings before you set up your automation. You cannot use Deep Clone as a Jira automation action without a preset.

Permissions

Make sure you have all necessary permissions. Deep Clone will execute clones in your name and with your permissions.

Make sure you have all necessary permissions. Deep Clone will execute clones in your name and with your permissions.

Use this to: Single clone the work item that triggered your flow.

• Enter {{issue.key}} as your Source Work Item Key.

• Select any Preset.

→ You can also use Jira workflows for single clone.

Use this to: Bulk clone work items based on a JQL query with all work item links still referring to the original work items.

Known limitations

When you bulk clone through Jira automation actions, work item links and hierarchies will not be logically recreated between your target work items. Instead, they will continue to reference the original work items.

Feature request: Send a feature request if you want more options to automate your

• Bulk Clone
  (full functionality, maintaining work item links, hierarchies and ranking)
  or

• Space Clone

• Before adding your action step:

  • Add Branch > Branch flow/ related work items.

  • Select JQL under Type of related work items.

  • Define the JQL query for the work items that you want to clone > Next

• Then:

  • Add Action > Deep Clone - Single Clone.

Use this to: Clone the work item that triggered your flow to multiple target spaces

• Create 2 or more presets with different target space settings

• Add the 1^st Deep Clone - Single Clone action to your Jira flow.

  • Enter {{issue.key}} as your Source Work Item Key.

  • Select Preset 1.

    

• Add the 2^nd Deep Clone - Single Clone action to your Jira flow.

  • Enter {{issue.key}} as your Source Work Item Key.

  • Select Preset 2.

    

You can add more Deep Clone - Single Clone actions to other spaces as needed.

Use this to: Log smart values from the cloned work item and use them as a filter to continue within the same Jira automation.

Example

• Add Action > Log action

• Add {{triggeredDeepCloneWorkItem.body}} as Log message.

• Add Branch Branch flow / related work items.

• Set id = {{triggeredDeepCloneWorkItem.workItemId}}as JQL.

• Continue the flow with any action you want.

More options

There are many ways to use smart values in Jira automations. Instead of logging {{triggeredDeepCloneWorkItem.body}} (as described above), you can use or log the following smart values in subsequent automation rules: Smart values.

Use this to: Log smart values from the cloned work item and pass them on to subsequent actions or Jira automations.

• Add Action > Log action

• Add any smart value as Log message

• Reuse the smart value in other Jira Automation actions, such as:

  • Send an email: Include smart values from the cloned work item in the email.

• • Trigger another Jira automation: Include smart values from the cloned work item in a webhook and reuse them in another Jira automation.

More options

There are many ways to use smart values in subsequent actions or Jira automations.

See:

→ Smart values

Use this to: Trigger other automated actions with Deep Clone.

See:

→ Use Deep Clone as a Trigger (via Webhook)

{{issue.key}}

The key of the work item that the automation is currently processing.

{{issue.project.id}}

The id of the space that contains the work item the automation is currently processing.

{{issue.issueType.name}}

The name of the work type of the work item the automation is currently processing.

Go to the Atlassian Documentation for more smart values provided by Atlassian.

{{triggeredDeepCloneWorkItem.allWorkItemIds}}

A comma-separated list of the ids of all work item clones that the action created. If the action has status SUCCESS, PARTIAL_SUCESS or ERROR, this list contains all created work items. For other statuses, the list only includes the work items that have been created so far and further work items might be created as the clone continues to run in the backend.

{{triggeredDeepCloneWorkItem.body}}

All information returned by the Deep Clone action.

{{triggeredDeepCloneWorkItem.spaceId}}

The id of the space in which the action created the first work item clone.

{{triggeredDeepCloneWorkItem.spaceKey}}

The key of the space in which the action created the first work item clone.

{{triggeredDeepCloneWorkItem.status}}

The status of the clone action at the time that the action returned control to the automation. As automations action have a maximum runtime of 25 seconds, the action might return before the clone is finished, which will be indicated in this output field. The possible statuses are:

• INITIALIZED: The job is not finished yet. So far, no work items clones have been created.

  • CREATED: The job is not finished yet. At least one work item clone has already been created.

  • SUCCESS: The job is finished. All work item clones have been created.

  • PARTIAL_SUCCESS: The job is finished. Some work item clones were created successfully, some work item clones could not be created due to errors.

  • ERROR: The job is finished. No work item clones could be created due to errors.

{{triggeredDeepCloneWorkItem.workItemId}}

The id of the first work item clone that the action created.

{{triggeredDeepCloneWorkItem.workItemKey}}

The key of the first work item clone that the action created.

{{triggeredDeepCloneWorkItem.workTypeId}}

The id of the work type with which the action created the first work item clone.

{{triggeredDeepCloneWorkItem.workTypeName}}

The name of the work type with which the action created the first work item clone.

{{triggeredDeepCloneWorkItem.allWorkItemKeys}}

A comma-separated list of the keys of all work item clones that the action created. If the action has status SUCCESS, PARTIAL_SUCESS or ERROR, this list contains all created work items. For other statuses, the list only includes the work items that have been created so far and further work items might be created as the clone continues to run in the backend.

{{triggeredDeepCloneWorkItem.messageJson}}

This field contains warning and error messages generated during the clone process. The JSON object has the following structure:

• {
    "<SourceWorkItemKey>: {
      <CloneActionKey>: <Messages (comma-separated)>
      ...
    }
  }
  

  For example:

  JSON

  {
    "TEST-1": {
      "reporter": "Reporter was not among editable fields.", 
      "assignee": "You do not have permission to edit issues in this project."
    }
  }
  

To keep access to an earlier output:

• Create a variable and store the smart value in it.

• Reference this variable whenever you need to access the earlier output.