Setting remaining estimate to 0 for closed issues

I have a lot of closed issues where my developers forgot to set the remaining estimate to 0. I can't edit them without re-opening them. Is there any way to bulk-change them?

5 answers

1 accepted

2 votes
Renjith Pillai Community Champion Aug 15, 2012

In simple terms

1 vote
Renjith Pillai Community Champion Aug 15, 2012

I am not sure whether I got your question right as Jobin already said reopening is needed anyway. Anyway my answer as per what I read from your description:

You can add an additional workflow transisiton (destination step as the Closed itself) in your workflow to clear off the editable flag for the issue. Once done you can do a bulk edit and also select not to notify the users while editing.

that sounds great. Could you give me advice on how to change that workflow accordinly. Sorry, I am a JIRA newbie and find the work-flow stuff a bit hard :)

I am loathe to dredge up an old thread, but this is still the most accurate advice, albeit with a quick update:

In my OnDemand JIRA configuration, I am unable to edit any of the time tracking fields as part of a bulk change. I had to add a transition post function to set the remaining estimate to 0 on close, and then bulk close the issues. This was what I wanted to do in the first place, so it worked out well, but this may trip other users up so I wanted to specify.

The transition post functions are available when editing a workflow by clicking on the resulting status. There will be "Conditions", "Validators", and "Post Functions". Click "Post Functions", click "Add Post Function", scroll to the bottom and select "Update Issue Field", click "Add", then select "Remaining Estimate", and enter "0m" for the remaining estimate. Now, when you perform the bulk change, the remaining estimate will be set to 0, and this will happen for all future issues being closed this way as well.

As per JRA-5034, it's currently not supported to set the remaining estimate via Bulk Change. sad

So it's either setting one by one or write a script for that...

For the future, you can set up your workflow to modify Remaining Estimate to 0 when the issue is transitioned to Resolved/Closed status.

0 vote

Reopening them is the only way to do this from UI. An easy option would be to fix this in JIRA but that would need an outage and reindexing.

Writing a script would be another option.

Suggest an answer

Log in or Join to answer
Community showcase
Jason Wong
Published 28m ago in Agility Beta

Welcome to agility

Every team in the world is unique, and so   Atlassian believes   that each and every team's best way of working   must be molded to their unique circumstances  – type of s...

11 views 1 3
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot