What is the difference between "Current Issue" and "Trigger Issue" in an automation rule?

[Benjamin Peikes]

We're creating some automation rules which create tickets. In the step to create the new ticket, we see that there are options of copying fields from the "Current Issue" or from "Trigger Issue". What is the difference between them?

I understand what the "Trigger Issue" is, but I'm not sure what the "Current Issue" is. They seem to do the same thing though.

[Jack Brickey · Accepted solution]

The trigger issue is fairly obvious so I expect the real question is when does current issue differ. This can happen if you use a branch rule. For example let's say you create a sub task when a task is created. Then you create a branch rule for that sub-task you just created now the"current issue" is the sub-task not the task (trigger issue). I hope this makes sense.

[Bill Sheboy]

Hi @Benjamin Peikes 

Yes, and to what Jack said with an example:

• trigger...   triggerIssue == current issue {{issue}}
• condition... triggerIssue == current issue {{issue}}
• branch... triggerIssue == current issue {{issue}}
  • stuff inside of branch...  triggerIssue <> current issue {{issue}} as current comes from what the branch found
• action... triggerIssue == current issue {{issue}}

Best regards,
Bill

[John Funk]

Hi Benjamin,

You can actually copy fields within the new issue to another field. For instance, copy the Approver field value to the Assignee. Or one date in the current issue to another date field in the same issue.