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

Cannot automate setting field "Original Estimate"

When I try to do this the audit log describes the error with:

"Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -Time tracking (timetracking)"

So I think I need to set permissions right some where. 
But what confuses me is, that the "Original Estimate" field does not exist in the "Custom Fields" menu, nor does "Time Tracking".

Also when I view the task that I have created with automation I can easily edit the Original Estimate field manually which heavily puzzles me vs then getting the information that the automation doesn't have permission.

See here, this is the field I want to edit with automation just like I do with other fields such as "Labels", but I can't even though I can easily change it manually:



Help would be super appreciated!

3 answers

1 accepted

0 votes
Answer accepted

Wow I just solved it but I would kind of consider it a Jira bug, solution was to set original estimate after the subtask was created instead of when it was created, that seems very unintuitive and the audit log does a poor job describing why this work around is needed with the permission hints.

See solution here:


0 votes
Daniel Ebers Community Leader Jul 22, 2021

Hi @Stef Green

could you probably show you rule alongside with the log? This makes it sometimes easier for Community members to follow.

One wild guess: have you checked if the executing user of the rule has indeed the "Work on issues" permission in your project?

I found it in documentation about time tracking ( it seems to be needed.


Thanks yes let me give you a bunch of screenshots here:

This is the audit log on the rule and red marked the error and the rule that spawns the error here:



This is how I set Original Estimate when I create the new sub task, note that I've also tried with syntax 2d, which caused no difference:

Also have permission on, not sure if I can grant more broad permission than this, also my account is admin and I'm the owner of the rule:

0 votes
Joy Chiu Atlassian Team Jul 20, 2021

Hi @Stef Green 

According to the message in the audit log, it is possible that the custom fields are not enabled in that particular issue type. Maybe you can check what type of issue will be created in the rule and check that config of the issue type.


Joy [Automation for Jira]

Thanks, to clarify the issue it creates is a Sub-task which uses the default issue type scheme which includes Time Tracking.
And I believe Time Tracking is what enables the "Original Estimate" field, but that part is super confusing, cause  normally fields exist by themselves, but the "Original Estimate" field does not, it's just shown in connection with Time Tracking.

Joy Chiu Atlassian Team Jul 22, 2021

Hi @Stef Green 

Can you try to create a subtask to see if you can set Original Estimate field when creating? Or share a screenshot with us about your configuration. And here is a reference about change the time tracking:



Joy [Automation for Jira]

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Apps & Integrations

Marketplace Partner Spotlight: AppLiger

This month the spotlight is on AppLiger. We caught up with Pavel Pavlovsky, CEO and Product Manager, to learn how the company started and what fuels the team's creativity.    Atlassian:...

331 views 0 7
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