How I can bulk update "Original Estimate" values from an excel csv in days like "1d, 5d, 13d, etc.)

[Jawed Ali]

Thru Import option all fields were created except Original Estimate. It shows "0m" against each issue Instead of csv column values in days

[Petter Gonçalves · Accepted solution]

Hello @Jawed Ali

Thank you for reaching out.

As you can see in the official documentation of CSV import, Time Tracking fields (Time Spent, Original Estimate, Remaining Estimate) can only be imported in seconds using the CSV import functionality.

The only exception would be if you set your time tracking to be estimated in minutes. In that case, the import of CSV files should also be added in minutes due to the bug below:

When importing issues from CSV, Original Estimate is imported as minutes instead of hours 

Additionally, we understand that "second" is not the most desirable unit to import time tracking fields, so we created the following feature request to allow other units:

CSV Importer Time Estimate should be able to configure other time formats than just seconds 

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

Let us know if you have any questions.

[S_ Francoeur]

According to https://jira.atlassian.com/browse/JRACLOUD-71406, some fields are incorrectly listed as available in the documentation for Bulk Update from CSV.

It is saddening that a "Severity 2 - Major" Documentation Bug –which would be relatively easy to fix– was inconveniently closed...

[Mark Mulik]

I have the same problem. I have been attempting to follow the instructions on how exactly to put the data in my CSV for Original Estimate so that when I import the CSV SOMETHING will show up in the Original Estimate field. I'm a system admin and am using the External System Import on Jira v8.20.2. 

Yes, I have the Original Estimate field available in my target project. I don't have any mapping problems. When I attempt to do the import, I experience one of these two things:

1. I get no import errors, but Original Estimate is blank for the imported issues. 
2. I get import errors, and the Original Estimate is still blank. The import errors refer to the Date format.

I find it strange that the date format field is required and has any effect on a field that apparently only accepts seconds for data entry. While that seems strange to me, I can live with WHATEVER the unit of time measurement is in, if the thing would just work at all. 

This is what the Date format field defaults to:

I have monkeyed with the field contents of Date format, attempting to use h:mm, mm, mmm, m, s. I have even blown away the field contents and left it blank. None of that works. I have monkeyed with the CSV file, trying these formats: number by itself, such as 1800; 1800s, 60m, 1:00. None of these formats works. 

I am missing key pieces of information on how to make this work:

A. How exactly do I format the data in the CSV for the field I am mapping to Original Estimate?

B. How do I configure the Date format field to successfully import the data in seconds for Original Estimate?

If you know, please provide an example CSV file and details regarding the Date format field.

It seems something simple must be escaping my notice on this, but I can't figure it out. 

Thanks for any help you can offer on this. 

Cheers. 

    Mark

[Miguel Rodriguez]

Just to clarify I am using 8.20 datacenter version and I successfully imported the original estimate field values using the CSV utility. You have to consider the values have to be in seconds without any other suffix or unit. In my case the source system had the values in days, and I was struggling to  get the right value in Jira. So after checking some of the imports I realized I had to consider the number of hours per day configured by the administrator in my instance. n our case it was 7.5 hours per day, so to convert the value (e.g. 30 days) to what the CSV has to have I used 30*7.5.60*60 = 810000 seconds. Once I used that value and imported the issue using CSV importer, it ended properly as 30d in Jira UI. 
so bottom line, before importing convert your original value (in hours, days, weeks, whatever) to seconds keeping in mind how many hours per day are configure in your jira instance and then express that value in seconds without any unit or additional character just the plain number of seconds.