Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Jira Automate Value Change For Trigger Does Work On Issue Creation

I have an automation that creates a series of stories when a component is added to an Epic using a compare two values and a variable to look for the component name in the {#changelog.component}},{{toString}},{{/}}.

The automation works fine if the component is added to the Epic after the Epic is created but when it triggers when the Epic is created the {#changelog.component}},{{toString}},{{/}} is blank and so the automation does not run.

Does anyone have any ideas on how I can get the automation to run on Epic creation without needing to create 2 separate automations?

1 answer

1 vote
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 09, 2023

Hi @Daniel Lupton 

Without seeing the details of your automation rule...

As you are using the changelog to determine what to add, you would need two rules: updated would use the changelog and created would use all values in the field.

Kind regards,

Thanks Bill,

I was afraid i was going to need to use 2 separate rules. Trying to find a way to avoid it but its not looking like I can.

Suggest an answer

Log in or Sign up to answer