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

Trying to set remaining estimate to zero when a story is closed but its not working

Using Jira v8.4.0 and trying to set story level remaining estimate to zero when its closed and its not working


Used Edit issue and JSON 

"fields": {
"timetracking": {
"remainingEstimate": "0",
"originalEstimate": "{{timetracking.originalEstimate}}"

But it errors as below as extracted from audit log. I added a comment fld at the end just to see if its getting values for originalEstimate and remainingEstimate and it does as I can see the values in the comment field

Edit issue

No fields or field values to edit for issues (could be due to some field values not existing in a given project):NIP-15474Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -Time Tracking (timetracking)

Comment on issue

Comment added to issue{{timetracking.originalEstimate}} {{timetracking.remainingEstimate}}


Also tried using system field "Remaining estimate" and it didnt work either.

1 answer

1 accepted

I tried solving myself.


Looks like Jira automation cannot edit fields once the trigger is on an issue being closed as it perhaps doesnt find the object/fld anymore. So I had to add addl. action to transition the issue back to "Re-opened" status and edit the remaining estimate fld and then transition back to "Copy from trigger issue" status which is either closed/done in my case.


Also I leveraged edit issue fld "Remaining estimate" and didnt need to use smart value/JSON

@Sreerampavankumar Govindarajula did you end up setting up the JA specific for transitioning to Close, or is it a job that works on any transition?  I have the same exact problem trying to update a field, because our Closed status has  jira.issue.editable property set, and we don't want to remove it.  (and thus, by the time the trigger fires, the issue is closed, and uneditable).

I would prefer to find a way to temporarily change that property to do the editing, but I think your solution is better for containment to just editing that issue.

Suggest an answer

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

Jira Automation: Sum Up Story Points Roundup (Initiatives -> Epics -> Story/Tasks -> Subtasks)

Hi Everyone, In this roundup we combine all the jira automation rules to sum up story points across different issue types. We start from the lowest level, summing up story points from sub-tasks t...

1,882 views 2 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