-
Bug
-
Resolution: Unresolved
-
Low
-
14
-
Severity 3 - Minor
-
5
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Problem
When user log work for a date that is different from the actual time, the CSV export only shows actual date.
Steps to Reproduce
- Log work for a different date than the current time
- Export this issue using the Export Excel CSV (All fields)
- Check the work log fields on the exported file
Expected Results
You can find the log work date.
Actual Results
You can only see the date when the log work was submitted.
Workaround
There are some possible workarounds to get the correct value:
- The endpoint Get issue worklogs returns the field started, which is the field that contains the date entered in the log work rather than the date from when the entry was created
- The endpoint to perform advanced searches is able to return the worklog field, and it will contain the started value as well
- E.g. /rest/api/3/search?jql=filter=10014&fields=key,worklog
- Our integration with Google Sheets or Jira Cloud for Excel offer the option to export the started value as well. Although if you need the worklogs in order to import values into a Jira instance it would require some manual work to merge the cells correctly:
- is related to
-
-
- Gathering Impact
-
-
JRACLOUD-80353 [Tracking in issue links] Date time format issues (system, custom, all views and inputs)
- Gathering Interest
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
[JRACLOUD-77926] When user log work for a date that is different from the actual time, the CSV export only shows actual date.
I also need a resolution for this, defiantly seems like an error....
I would like a resolution for this issue.
Echoing Jim's comment above, what does Timed Out mean?
I do a server backup that exports raw XML. Parsecthe XML for <worklog> records. Swap the dates as this backup has the correct dates in it.
Another user looking for a resolution to this, or a workaround. How can work log be exported with the correct dates?
If this is going to be fixed, I'd like a heads up to understand what changed. I wrote a work around that relies on how the <Worklog> tag is built.
Alan Burton
added a comment - Thanks Jim. A lot of work for what I would think is a straight forward issue to resolve.
Alan Burton
added a comment - Thanks Jim. A lot of work for what I would think is a straight forward issue to resolve. I ended up writing code external from JIRA to fix this issue. I noticed that an export does include the correct dates. So I use run a backup which produces an export file. I parse the export file and reconcile the JIRA ticket number with the backup. I then use the date from the export instead of the JIRA ticket.
Alan Burton
added a comment - The impact of this issue is that customers can't use the exported data for accurately tracking and reporting on work logged / developer. Hoping this gets prioritised soon.
Alan Burton
added a comment - The impact of this issue is that customers can't use the exported data for accurately tracking and reporting on work logged / developer. Hoping this gets prioritised soon. The description should say:
When a user logs work for a date that is different from the date when the log entry was added, the CSV export uses the date the log entry was added, not the date the work was done on.
As a result, the export cannot be used for external time reporting as the work shows up being done on the wrong date. For example, if a developer logs all of their time first thing Monday morning for all of the work for the prior week, all of the work shows as being done on the Monday, not for the previous week. This leads to curious issues where a developer shows they worked 37.5 hours on one day. Trippy.
I didn't expect this behaviour and am now having to use the Google Sheets integration to work around it.