How to use "Current issue vs Trigger Issue" for "Create or Edit Issue" action in the Jira automation

 

Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.

   

Summary

Create Issue and Edit issue actions have a feature to automatically copy value from “Trigger Issue” or “Current Issue”. Both of these have different behavior. This page will explain how to use it.

Environment

Jira Automation Cloud

Solution

Trigger Issue: We need to use Trigger Issue (instead of Current Issue) in the copy option in the "Create issue or Edit issue" action in the automation rule to copy the field values from the issue that triggered the rule to copy the field to a custom field or a project.

For example: Here is an automation rule wherein we need to copy the Jira field values from the trigger issue when the "Priority" field value changes in the same ticket as well as in the new ticket created in another project.


Current Issue: We need to Current Issue in the copy option while using the "Branch" Option for the current issue.

For example: Here is an automation rule wherein we need to copy the Jira field values from the current issue when a new issue is created. Hence, when we branch on the current issue (for which the rule is executing), we use "Current Issue" to copy field values in the same ticket as well as in the new ticket created in the same or another project.


Last modified on Oct 31, 2023

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.