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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Custom Field JSON works On Change Value not On Issue Create?

Why does below JSON not work On Issue Create, while it does work On Change Value?

{ "fields": { "summary": "Use my custom field: {{MyField}}" } }

2 answers

0 votes

Hi @Ron Koudijs 

  • Would you please clarify what problem you are trying to solve?
  • And, when you note it does not work on issue create, what do you observe happening?

I note you posted this question in the automation area; are you doing this with an automation rule?  If so, there are known race-track issues with issue create triggers.  One work-around is to re-fetch the issue before processing to ensure the data is present.  For example:

  • trigger: issue created
  • action: re-fetch issue
  • ...continue with your rule processing


Best regards,

Hi @Bill Sheboy 

Yes, I am trying to change the summary field with automation. For the summary I want to use custom fields. I tested the JSON code with a "When value changes for" + "Edit issue fields". That works fine. But the same JSON code with a "When issue created" does not give a result.

I am going to try your re-fetch suggestion.

Thanks for helping.



Like Alexander Pappert likes this

I found the reason of my problems. We are using Dynamic Forms from Devinity. The issues I am having trouble with are created before the Dynamic Forms is filled by the customer. Deviniti suggest a work around with a time in status" trigger. I'm still figuring out how to get this (SLA?) tigger to work. To be continued ;-)

Like Bill Sheboy likes this
0 votes

on issue creation, the custom field is not filled/existing. thats why ist doesn't work there

So it is impossible to automate based upon custom fields? Strange! What is the work around? Can I automate / create a trigger "just after creation"?

or, as @Bill Sheboy wrote

action: re-fetch issue

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events