Why "original estimate" field is not available while doing bulk update?

Question

I've uploaded a bunch of test cases through the XML report, and now I want to add all the mandatory fields through a bulk update so that I can move those test cases to the ready-for-execution state. Still, the original estimate is mandatory to change the status of test cases. There is no way I can add the original estimate in bulk as the original estimate field is not visible. Please suggest a solution.

Hannes Obweger - JXL for Jira · Answer

Hi @ritu.goswami

welcome to the community!

Just to add to Callum's answer: f you open to solutions from the Atlassian Marketplace, this would also be easy to do with the app my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also supports bulk editing via copy/paste - for all editable issue fields, including the original estimate.

This is how this looks in action:

This works for any number of issues in one action - so you should be done with your work in no time!

Any questions just let me know,

Best,

Hannes

Callum Carlile _Automation Consultants_ · Answer

Hi @ritu.goswami , welcome to the Atlassian Community!

Unfortunately this is not possible -  there is this open feature request to implement this, so feel free to give it a vote and watch it if you want to receive updates to it.

If you have a small amount of tickets, then you can create a simple automation rule to bulk edit these values (assuming that you are wanting to set the field to the same value for all tasks):

* Create a Scheduled automation within the trigger use a JQL to find issues with empty original estimate (originalEstimate is EMPTY)
* Add an Edit Issues action, select Original Estimate from the dropdown and enter the value you wish to set
* Once you create the automation, press on Run rule button and check the audit log to view the execution of the automation rule