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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Unknown fields set during create using JSON

Hi, i am trying to use this code for setting the "Status" field to 'something' in the Additional fields section..for some strange reason the "Status" field is not recognized..i receive this error message:

'Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -Status (status)'


...but the field is clearly visible in my task layout..


"fields": {
"status": "SOMETHING"



What am i doing wrong here?

3 answers

1 accepted

0 votes
Answer accepted

Thanks for your reply Gareth,

my automation rule is based on a task being created on a schedule, as i am applying the Transitioning the new task does not receive this value, but the Epic that is scheduled does, apparently i am doing something wrong here...

Hi Peter,

I'm assuming you are using a Create issue action somewhere in your rule. If this is the case, you can follow it with a Branch rule/related issues component set to "Most recently created issue" which will act on the last issue created in the rule and then use the transition issue action inside that

Hi @Peter Fahlstrom 

The status field is set by transitioning the issue through the workflow which is why you cannot set it directly.

When an issue is created, it will be set to the status linked to the Create transition of the workflow.

You will need to use the Transition issue action in an automation rule to move the issue to the correct status.

I was too fast in my reply, i added a branch rule prior the Transition rule with the definition of 'For All created issues' and that looks to be working..



You figured it out just as I hit send on my reply 😄 

Like # people like this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Automation

Announcing the Jira automation template library!

Hi all,  After many months of work, I am delighted to announce the launch of the Jira Automation Template Library!  The Template Library is a new website dedicated to all things Jira au...

694 views 12 20
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you