-
Bug
-
Resolution: Unresolved
-
Medium
-
20
-
Severity 3 - Minor
-
82
-
Summary
When importing issues from CSV, despite estimates being listed in seconds according to Creating Issues using the CSV Importer and Importing Data from CSV, if default unit for time tracking is set to minutes, it will be imported as minutes instead of hours.
Environment
JIRA 6.5.*
Steps to Reproduce
- Set Time Tracking default unit to Minutes (per Configuring Time Tracking)
- On a JIRA instance, Issues > Import from CSV
- Import the attached CSV
- Check the imported issues. Original Estimate will show 14m instead of 14h.
Expected Results
Importer would convert the seconds to minutes and then hours/days if necessary.
Actual Results
The minutes are converted to hours and then labeled as minutes. The default unit should only be used if not specified.
Notes
For example, Original Estimate is listed in CSV as 50400 seconds > 840 minutes > 14 hours
Importer converts the 14 hours back to minutes, by default.
Importer should know that 50400 is listed as seconds.
Solution / Workaround
- Change Default Time Tracking unit to hours, and re-import the CSV issues.
- Confirm that Original Estimate shows correct time, and if desired, change the default time tracking back to minutes.
- is related to
-
JRACLOUD-65813 Time Tracking Fields not imported correctly by Issues --> Import from CSV
-
- Closed
-
-
JRACLOUD-68578 Original Estimate CSV values less than 1h will not import from issues import when time tracking set to Hours
-
- Closed
-
-
JRACLOUD-81952 Time spent and and Total time spent field adds up during CSV import
-
- Gathering Impact
-
- is duplicated by
-
JIM-1529 Failed to load
https://getsupport.atlassian.com/browse/CES-52272