Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Can you import the "Original Estimate" when the issue type is "Epic"?

Amber Thomas
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!
June 16, 2025

I've completed the import of issues via the import function before and was able to import the Original Estimate in seconds.  However, when the issue type is "Epic" instead of "Task", the import doesn't work.  I don't get any errors on validation; however, the Original Estimate field isn't updated even though the field is mapped.

1 answer

0 votes
Gor Greyan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 17, 2025

Hi @Amber Thomas

Welcome to the Atlassian Community.

The issues root cause may be different. I will tell some points to check, but also ask to provide an example from the mapping file, on how it is structured.

1. The Original Estimate field is part of the "Time Tracking" system.  If your Epic's screen doesn't include the "Time Tracking" field, Jira will not store the estimate field.

2. The header of the import file should be correct - like this: Original Estimate

3. The value of Original Estimate have correct format: 1h, 3h 30m, 1d

If the above-mentioned is okay on your side, kindly ask you to provide a screenshot or example of how the import file is. 


Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events