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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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

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

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Apr 18, 2023

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.

2 answers

1 vote
Callum Carlile _Automation Consultants_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 18, 2023

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
0 votes
Hannes Obweger - JXL for Jira
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Apr 18, 2023

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 up to 10000 issues in one action - so you should be done with your work in no time!

Any questions just let me know,



Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events