Validation error when performing worklog field update via CSV import when the value is in seconds format

Summary

When importing worklog field values into Jira issues via CSV import, a validation error occurs if the worklog value is provided in seconds format.

Diagnosis

Scenario 1:

When importing the Worklog field values on Jira issues via CSV import wherein the value is in seconds format, the following error may be seen:

Worklog for the issue with id XXXXX did not pass validation due to errors Errors: {timeLogged=Invalid time duration entered.} 

Example value: 70 (70 seconds to indicate 1 min 10 seconds)

Scenario 2:

The user wants to import the values of the time tracking field in days, hours and minutes via CSV, however, the value is imported either in days or hours

Cause

Scenario 1: The above-mentioned error occurred as the "Default unit" of the Time tracking setting is set to "Minute" and the value in the CSV file has been passed in seconds hence causing the validation error.

Scenario 2: Due to a discrepancy in the time setup. If the time display format setting is configured in "hours" or "days" rather than "Pretty (e.g., 4 days, 4 hours, 30 minutes)" format, then the value would be visible in Days or Hours format.

Solution

Scenario 1: Please update the time value in the CSV file as per the Default Unit size set in the time tracking settings.

Visit your time tracking configuration: https://yourjirainstance.atlassian.net/secure/admin/TimeTrackingAdmin.jspa

Scenario 2: In order to mitigate the behaviour, the time tracking setting should be displayed as Pretty (e.g., 4 days, 4 hours, 30 minutes) instead of hours or days.

For assistance in changing the time tracking configuration, follow the document: Configure time tracking

It is also important to ensure that the value of the Worklog field in the CSV file is defined according to the Default unit, like minutes.

An example for 1 hour of Worklog CSV should be: