nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

CSV import - original estimate

Natia Chincharauli

Hey Team,

I am trying to create issues from CSV with original estimate time included. (See picture 1 below) Tried to insert in 30m/30 minutes/30/1800 formats and none of it worked. When an issue is uploaded, original estimate stays 0 minutes. (See pic 2)

Can you please, assist?

Pic1 Screenshot 2022-01-24 at 14.46.52.png

Pic2

Screenshot 2022-01-24 at 14.48.20.png

Accepted answers

Tansu Akdeniz

Hi @Natia Chincharauli

Original estimate value needs to be specified as second.

I guess you properly match the original estimate field within import wizard. Did you have a chance to investigate detailed log file which becomes available after import process?

Also please take a look: https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/

Pramodh M

Hi @Natia Chincharauli

You should be able to import the issue with the Original Estimate. You should input the value in seconds

Here's the reference (https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file)

This is the page we get while importing

Sample CSV File

Summary,Issue key,Status,Original Estimate
Issue 2,PT-2,Done,3600

Thanks,
Pramodh

All comments

Tansu Akdeniz

Hi @Natia Chincharauli

Original estimate value needs to be specified as second.

I guess you properly match the original estimate field within import wizard. Did you have a chance to investigate detailed log file which becomes available after import process?

Also please take a look: https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/

Pramodh M

Hi @Natia Chincharauli

You should be able to import the issue with the Original Estimate. You should input the value in seconds

Here's the reference (https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file)

This is the page we get while importing

Sample CSV File

Summary,Issue key,Status,Original Estimate
Issue 2,PT-2,Done,3600

Thanks,
Pramodh

Natia Chincharauli

Thanks Pramodh,

the problem persists since there is no specified time frame when I map original estimate. For 3600 value (which should be 1 hours) is uploaded as one minute in jira. Screenshot 2022-01-24 at 16.42.48.png Screenshot 2022-01-24 at 16.48.46.png

Filippo_94gsgb

This bug persists. 72000 seconds is converted as 20 minutes rather than 20 hours.

dmitriy_landa

The issue still there

zacharoula_brinia

Any update on the above issue?

Dean Ritchie_n5v2as

Still seeing this issue. Terrible work around, multiply by an additional 60 to turn your minutes into hours.

So If I want a 2 Day estimate the math is: 2 Days * 8 Hours * 60 Minutes * 60 Seconds * 60 JIRA TIME = 3456000 JIRA Seconds.

I'm sure one day it'll be fixed and suddenly everything will be 60X too long, but we'll see.

Edit: Since people are still having issue check what your instance has for work hours per day. Our jira uses 8 hours which is why I'm using it above.

unknown

Just verified this today, thank you for the terrible workaround. I did really enjoy the "* 60 JIRA TIME" though.

modder2

@Dean Ritchiethank you! You helped me solve this problem!

Rogerio Pellarin

I would like to solve the issues in my software as Jira does: they removed the option to import the original estimated. When you find bugs, you delete them!! Easy busy!

Ariel Ramos_lss9b2

@Dean Ritchie Yeey!!! This has been bugging me for hours now. Thank you very much for sharing the solution~ 😊

Edit: And it looks like everything changes again 😑. It looks like there's no longer a need for an additional "Jira Time" for importing CSV. Back to what it should suppose to, I guess.

Neal Anderson

I too ran into the need to use an extra Jira Seconds multiplier of 60 to get a proper number of "seconds" loaded into the OrigEst field, to show properly as my target number of hours in my tasks.

Then... I added Story Points to my CSV file, so I'm loading both OrigEst and StoryPoints. When doing this, I noted that my OrigEst hours were now off, too large by a factor of 60. It's as though adding the Story Points into the CSV load process somehow corrected the calculation of seconds used in the OrigEst field. Weird...

Slim ALOUI_ngfxvn

I still have the bug. just multiply by x60 after the number in seconds and it would be fine.

Dhananjay Kale

We are also facing the same issue (JIRA DC v9.4.10).

Values for Original Estimate are

4320 Seconds ==> 72 minutes ==> 1 Hours, 12 Minutes

2880 Seconds ==> 48 minutes ==> 0 Hours, 48 Minutes

7200 Seconds ==> 120 minutes ==> 2 Hours, 0 Minutes

When we import issues through (as JIRA Administrator) Administration >> System >> External System Import >> CSV import, the values are imported correctly

4320 Seconds ==> 1 Hours, 12 Minutes

2880 Seconds ==> 0 Hours, 48 Minutes

7200 Seconds ==> 2 Hours, 0 Minutes

But when we import issues through (as Non-JIRA Administrator) Issues >> Import Issues from CSV, the values are NOT imported correctly

4320 Seconds ==> 1 Hours, 0 Minutes

2880 Seconds ==> 0 Hours, 0 Minutes

7200 Seconds ==> 2 Hours, 0 Minutes

We tried to multiply them by 60 but the they are imported as

1 week 4 days

1 week 1 day

3 weeks

Any resolution for this bug?

-DJ

Slim ALOUI_ngfxvn

1 day (8hours of work) x = 1728000

If you want to have 1h then x/8= 216000

if you want 12h then it's 1 day and 2 hours so : x + 0,25*x = 2 160 000

Kirsten Yu

This horrible issue persists but I have found a solution thanks to everyone's contributions!

I put in 3456000 for my original estimate value and got 40d as a result.

From there, I divided 3456000 by 40 which gives me 86400.

I did another upload with 86400 for my original estimate and voila! I finally got the 1d value I've been so desperately craving for!

TLDR - put in 86400 for 1d, write this number down to use/adjust for future uploads!

Dhiman Ghosh

I have the same issue where only whole hours are accepted. Any solutions to this?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

atl-gruland