keith@atlassian.com  PLEASE REOPEN AND FIX THIS PROPERLY !!!

16e17ad0ff63 this is definitely not implemented in Jira Cloud, could you please retest and update this as necessary. Many thanks

16e17ad0ff63 Why is this marked as fixed, while only a very small part of the solution is given??
A simple bulk change edit on a JQL search for example does not even work...

PLEASE REOPEN AND FIX THIS PROPERLY !!!

Hello everyone, Original Estimate and Remaining Estimate (Time Remaining) fields are now available to bulk edit using Bulk Edit in Backlog, Bulk Edit in List View and Bulk Ops REST APIs.

Disclaimer
Adding bulk editing capability to Time Spent field of the Time Tracking field was not in the scope of this JAC ticket. There is another JAC for the same: https://jira.atlassian.com/browse/JRACLOUD-84851. Please feel free to vote on the ticket and add yourself as a watcher if you want this feature.

really?? You implemented it for Server/Datacenter!!! How about some feature parity here.

Hi,

Sprint planning and capacity planning for Jira https://marketplace.atlassian.com/apps/1219264/sprint-planning-and-capacity-planning-for-jira?tab=overview&hosting=cloud  supports bulk updates of time and story point estimates, as well as other helpful features needed during sprint planning.

Best,
Jerry - Divim, Inc.

go to Cloud, they said

the newest features and implementation are rolled out there first, they said

20 years? are you kidding? 😂

>600 votes 😭

We've changed the developer and must re-estimate and re-do much of the work. Being able to bulk-clear the estimates and time-tracking would come in handy now. Now I have to spend hours reviewing each one and clearing the original estimates and worklog. 

Thank you Nicole. That works!

Hi Jon Platt,

A simple way is to set up an automation task.  I have set up a schedule to run every friday with a jql query "status = done and remainingEstimate > 0", then in the Edit issue action I chose the Remaining estimate field and set it to zero.

You could run the automation once to clear your current problem. You could then either disable the automation or remove if you don't want to use it in future

Darn! Just migrated from Server to Cloud and have only now discovered that bulk edit for estimates is missing. Not happy. I want to zero out remaining estimate for closed tickets. Any suggestions, other than reverting back to Server?

Oh I'm so sad to end here when setting a project roadmap for a 12 month project.... This should be a standard feature.....

My ScriptRunner script that I ran in the ScriptRunner Console to achieve this (run as the ScriptRunner Add-On User):

def jql = 'statusCategory = Done and timeestimate > 0'
def timeRemaining = 0;
def total = 0
def startAt = 0

while(total==0 || startAt<total)
{
    def result = get("/rest/api/3/search?fields=timetracking&startAt=${startAt}&jql=" + java.net.URLEncoder.encode(jql, "UTF-8") )
        .header('Content-Type', 'application/json')
        .asObject(Map)
        .body
        
    total = result.total
    startAt = startAt+result.maxResults
    result.issues.each {
            logger.info("original is ${it.fields.timetracking}");
            it.fields.timetracking.remainingEstimate = timeRemaining
            it.fields.timetracking.remove("timeSpentSeconds") // removed because it's not allowed to be updated
            it.fields.timetracking.remove("timeSpent")  // removed because it's not allowed to be updated
            logger.info("modified is ${it.fields.timetracking}");
            
        def pageResult = put("/rest/api/2/issue/${it.key}") 
            .queryString("overrideScreenSecurity", Boolean.TRUE) 
            .queryString("notifyUsers", Boolean.FALSE)
            .header('Content-Type', 'application/json')
            .body([
                fields: [
                    timetracking: it.fields.timetracking
                ]
            ])
            .asString()
        if (pageResult.status == 204) { 
            logger.info("Success on ${it.key}");
        } else {
            return "${result.status}: ${pageResult.body}"
        }
    }
}

HOW IS THIS NOT A BASIC FEATURE!!!!!!!!!! I have 55 tasks that just need to have a 2h estimate and i have to do it by hand. so dumb! 

Lack of this feature significantly limits csv task import. In case it would be available, once importing list of issues, it would be helpful to provide their estimates.

eabb54fc0692 My current need is...

I want to be able to bulk edit original estimate for sub-tasks. Sometimes scope changes so team estimation has to change. I always create sub-taks with «Import issues from CSV» so I can create hundreds of sub-taks. When scope changes takes so much effort to edit original estimate.

HI @Michal Gorski, 
Thanks for your feeback. I'll try for my projectsBUT honestly Automation management is not as easy as the Bulk update.
Automation needs more support and settings for teams while Bulk update, teams are really more autonomous and effective!
Best

Hi Celine,

I've struggled with it and then figured out a workaround.

Please have a look at my last post. It will work in your case. Remember that you should have at least a 'company-managed' project to use automation.

Good luck! 

Hi eabb54fc0692 

Based to the T-shirt sizing estimation (relative estimation), my current need is to have a macro estimation of the remaining work. /!\ These tickets have NO time tracking's original estimation.

ex : I want to select all the XL estimated tickets, then bulk update and insert a time value. 
M = 3 weeks
L = 10 weeks
XL = 15 weeks ...

We don't have Scriptrunner, neither Advanced Roadmap and I don't know how to use the API. We have to do it with a basic Jira Cloud version.

Many thanks by advance for your support.
Best

I ended up working around this using script runner, allowing my to make ad-hoc changes for issues matching some JQL.

def jql = 'filter = "my jql in her'
def timeRemaining = 0;
def total = 0
def startAt = 0

while(total==0 || startAt<total)
{
    def result = get("/rest/api/3/search?fields=timetracking&startAt=${startAt}&jql=" + java.net.URLEncoder.encode(jql, "UTF-8") )
        .header('Content-fType', 'application/json')
        .asObject(Map)
        .body
        
    total = result.total
    startAt = startAt+ result.maxResults     result.issues.each{
         
    def pageResult = put("/rest/api/2/issue/${it.key}") 
        .queryString("overrideScreenSecurity", Boolean.TRUE) 
        .queryString("notifyUsers", Boolean.FALSE)
        .header('Content-Type', 'application/json')
        .body([
            fields: [
       timetracking: [
          remainingEstimate: "${timeRemaining}",
originalEstimate: "${it.fields.timetracking.originalEstimate}"
       ]
    ]
        ])
        .asString()
    if (pageResult.status == 204) { 
        logger.info("Success on ${it.key}");
    } else {
        return "${result.status}: ${pageResult.body}"
    }
    }} 

It's pretty dirty, but it works.

A workaround if anybody is still interested in editing the time-tracking elements:

• Define a label (ie. "FireTimeTrackingAutomation") to assign the label to the elements that you'd like to bulk edit
• Wrap the action you'd like to perform in automation that will be triggered while setting the label
  • Trigger: Label is changed
  • Condition: Label = FireTimeTrackingAutomation
  • ie. Set remaining to 0 / THE ACTION
  • Remove the label in the automation (also in the automation) if you want
  • Put a comment (also in automation) if you want
• Find elements that you'd like to edit
• Bulk add the label

The automation will perform the ACTION for you.

Hi Everyone,

I'm interested in getting more details about your use cases for bulk editing time tracking estimates. Is anyone keen for a quick 30 minute chat?

Please feel free to respond here with your email address or book directly via this link: https://calendly.com/emditchfield/customer-chat 

Cheers,

Emily Ditchfield

Product Manager, Jira Software

18 Years in interest Gathering - WoW

Need this feature

We need this feature!! 18 years since this was created

critical element. that and story points.

Need this as well

Yes, i need this as well.

Folks, this issue is old enough to vote, I don't think it's gonna go anywhere. I had to dig out an ancient account to log back in to un-watch it so I stop getting pinged on other people also asking for it.  Good luck out there.

We definitely need this feature.

For me this feature is needed because of testing plugins create a lot of test issues, which efforts are so small that can be omit, but still they appear as not estimated issues in the reports. This feature can easily make them all estimated to 0.

As a workaround, you can configure an automation to set the remaining estimate to X when an issue is transitioned to a state.

We use this automation: When issue is transitioned to Done, then edit issue field Remaining Estimate.

I could have used this feature so many times already. It means that now I'll need to manually update 22 cards and colleagues will get spammed with emails about these changes.

Please re-evaluate this.

Still a desperately needed feature. Please re-evaluate the 2016 response.

+1

Just migrated from Jira Server to Jira Cloud, huge regression from my point of view 
We need this to easily close issues and erase remaining time on tasks

+1

Hi

At Divim, we saw our customers struggling with this issue and we created Backlog refinement and Sprint planning.

https://marketplace.atlassian.com/apps/1220864/backlog-refinement-and-sprint-planning?tab=overview&hosting=cloud

It allows you to find all the stories without an estimate (in story points), and all the subtasks without a time estimate. 

Let me know if you would like to see other features as well.

Jerry

+1

+1 We need this. Why is it only available for the Server version? Jira Cloud should also offer this!

+1

@dmeyer Testing mention functionality (b/c they seem to get used here, but there's no user lookup functionality available via Comment editor @ symbol invocation). Not sure if I'll be able to delete this, so apologies and please disregard if I'm unable.

+1

+1 From here too.

Much needed for daily project management tasks.

can we please get this feature? 

Very annoing, I miss this afer swiching to Jira Cloud.

I really don't understand why some things are omitted like this. We want full control, even when using the cloud version!

+1 

urgently needed for our daily operations and project management

I know this was fixed last year in Data Center, it would be great if users of Cloud could have these handy feature as well.

+1

Would really like to be able to bulk change time estimations.

Hello everybody. If I understand the issue here correctly, this is easily doable by just copying and pasting, using our spreadsheet app JXL: https://jxl.app

• Install JXL your Jira site
• Create a sheet inside Jira with all the issues you want to change (you can write JQL for this)
• Add the Original estimate column to the sheet (or whatever field you want to bulk change)
• Edit, mark and copy (⌘/Ctrl + C) a cell with the desired field value
• Mark multiple cells and paste (⌘/Ctrl + V) the copied value into them
• JXL takes care of the bulk change for you instantly

Hope that helps. It works with hundreds or thousands of issues.

Disclaimer: I'm co-founder of the app vendor behind JXL. Your feedback is welcome and much appreciated. There's a free fully functional trial available on the Atlassian Marketplace here: https://marketplace.atlassian.com/1224710 (check out the short demo video)

+1 we would like to have this feature

we need that feature

Bhuvnesh.Chandra, see the description at the top of the page: "unfortunately we don't have any plans to support this in JIRA for the foreseeable future".

Is this feature coming up or just a ticket is open  

+1 need for our team, as we just started using the time estimate this was requested.
 

NOT available for me as well 

I can't believe such an obvious feature hasn't been implemented in Jira Cloud yet. A 16 year wait and still not done even though it was for server over a year ago.

Just submit a ticket now and maybe by the time your new born child is ready to start college it will have been addressed. Simple! 16 years is entirely a reasonable time for an open ticket!

This is not available for me in Jira Cloud as well.

Still not available in Jira Cloud in my instance.

Jira Cloud does not mirror Server. A lot of Server features are missing from Cloud.

Should be available in Cloud version, as it is also available for server and data center.

Suggested workaround using Jira API is unusable for non devs - rather unsatisfying that you need to have your own Jira Admin developer although using the cloud version, specially, if this version is focussing on nice UI (beside confusing UX changes) instead of functionality.

Thanks

Can we please get this for the cloud?

This was implemented on Jira Server now - can anyone provide an idea of whether this will make it into Jira Cloud?

The Jira Server task has been marked as In Progress. Great news! Will that in progress feature work be passed to Jira Cloud?

Yes, this would be really great. Also, it should support third party plugins like tempo.

Working on a project where this feature would've helped to streamline some of the process in managing 600 issues.

andy.holvoet,

You can get a set of issues by calling the {{/search} endpoint with the ?jql= query parameter and a URI encoded string of JQL, e.g.

https://baseurl.atlassian.net/rest/api/2/search?jql=project%20%3D%20DEMO%20and%20%22text%20field%22%20~%20%22asdfasdf%22&fields=worklog

In this example I also passed worklog in the fields expansion to expand the worklog objects in each issue that is returned.

Each issue object contains a self URL that is the REST representation of the worklog, like this:

"worklogs": [
                        {
                            "started": "2016-09-07T00:00:00.000+1000",
                            "self": "https://baseurl.atlassian.net/rest/api/2/issue/10103/worklog/10300",
                            "updated": "2016-09-07T23:59:56.722+1000",
                            "issueId": "10103",
                            "id": "10300"
                            ...
                         }
               ...
            ]

You can then call the update worklog REST API to change the remaining estimate, like this:

https://baseurl.atlassian.net/rest/api/2/issue/DEMO-4/worklog/10300?adjustEstimate=new&newEstimate=50m

by using the adjustEstimate and newEstimate query parameters. In case I changed the new estimate to 50 minutes, but you could easily provide "0" as well.

The workaround is to write a script to make the initial REST API call to get the worklogs, parse the response, and then make each individual worklog update request.

Hope this helps.

Dave Meyer
Senior Product Manager, JIRA

Issue created on 25/Oct/2004 Nice of Atlassian to care about the input of their users...

@dmeyer Can you please provide a more specific link to the workaround you suggest with the REST API? Can you elaborate on how to set the remaining estimate to 0 with the REST API?

Please implement this, this is a feature we have needed at the moment. Affects version 6.4.12

@martin Gregory I would see it as at first a free thing to use as a lead magnet for a business agency or for another product. So you could promote your product and here are an email list from it. As people would only need it every 2-4 weeks for a minute or two. It would be a help and people will be likely to search For a fix. Also just take the names of everyone on here in 10 years of comments.

@Trista Bailey ... how much would you pay? How often would you pay? The problem for any small startup filling a gap like this is that it is crucial when you need it, but the typical user only bumps into it rarely. When they do, they are mad as hell that a basic feature like this isn't there, but its hard to see anyone subscribing even $5pm for this. Especially because no-one likes paying for features that should be in there anyhow.

To JIRA: Why not just close this ticket out if you're never planning on doing anything with it?

@Darren Pye I think we all agree.

What we need is a small startup with java or api skills to make a dashboard app for this, that at least grabs all at the end of a sprint and checks for 0s and adds to bulk edits, then back to JIRA for rest.

Money in them there Rock Hard hills

I'm planning a new release and we have a lot of items that need to be verified and I'm trying to update the items with times so we can get a sense of the scope of the verification process other than manually calculating. Being able to bulk update the time remaining or original estimate (as a work around) would make this easy. I was quite surprised to find out that JIRA, being a planning tool.... lacks such basic support for... well... planning Please add

+1

+1

+2016

+1

+1

Hi macnewbold,

Bulk Edit was introduced in JIRA 2.5, back in 2004. Unfortunately I wasn't on the team then so I can't provide any context on why it wasn't implemented originally.

As for why it isn't currently planned: in order to prioritize our work, we generally identify several themes or focus areas that we believe need the most attention, and develop our roadmap around that. Currently those top investments look like:

1. Performance/page response times
2. Simplifying navigation and key user experiences (boards and backlogs, search)
3. Reducing complexity around project configuration (all the different schemes)

You can learn more about our process here – while we pay quite a bit of attention to the comments, votes, and sentiments of feature requests on jira.atlassian.com, usually the age of an issue isn't a factor. We don't follow a "last in, first out" approach to our roadmap – we are continually re-evaluating to determine what we could do to improve reliability, usability, or functionality for the most customers today. The best improvement we could make for folks may be on a feature that didn't exist when this issue was created.

That's not to say I don't think this should be supported, I do. Just at a high level, there is this request at dozens and dozens like it, and simply have to prioritize with limited staff.

My email address is in the description if you would like to follow up.

Regards,
Dave

dmeyer, do you know why this wasn't available in the first place, or why it isn't planned to be corrected? People have literally been asking for it for over 11 years now...

Hi dmeyer thanks for your follow up. 99% of the times I need to bulk edit estimates is because the CSV Import did something wrong, like JRA-44971 and JRA-43546. Hope at least one of these issues get resolved by Atlassian.

Thanks!

+1

@DMeyer thank you for taking the time to review this feature request again.

We will keep +1uping and see if you are more interested next time.

Hi everyone,

Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; unfortunately we don't have any plans to support this in JIRA for the foreseeable future. In the meantime, we recommend bulk editing worklogs via the JIRA REST API

Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform

+1

Yes please