-
Bug
-
Resolution: Timed out
-
Low
-
1
-
Severity 3 - Minor
-
Issue Summary
When logging time to an Epic and its child issues, the field "Σ Time Spent" does not display the sum of logged hours in the Epic at the issue navigator, however, it displays properly when exporting the query to CSV, Google sheets, or Excel.
P.S: I found this suggestion describing this behavior, however, the suggestion incorrectly states this behavior does not reproduce for team-managed projects, which I confirmed it does. Additionally, it does not mention the discrepancy when exporting the query to CSV.
Steps to reproduce:
- Create a new Epic and log any time. E.g: 3h
- Create a child issue under that Epic and log any time. E.g: 2h
- Navigate to the issue navigator page and run any query returning the Epic you created
- Check that the time logged for the Epic is the same for both fields "Time spent" and "Σ Time Spent" (3h), so the field is not aggregating the time logged for the child issue:
- Click to export the issues to CSV, Jira Cloud sheets, or Excel
- In the CSV file/sheet, check that the aggregated time from the child issue is properly included in the field "Σ Time Spent" (displaying 5h in seconds):
Expected Results:
- The field "Σ Time Spent" in the issue navigator and CSV export should display the same values - The aggregated logged time in the Epic and its child issues.
Actual Results
- The issue navigator does not display the aggregated time for the field "Σ Time Spent", while the CSV export does.
Workaround
None so far.
- is related to
-
JRACLOUD-82605 [Tracked in Issue Links] tickets related to issue exports (CSV, HTML Report, Excel etc)
- Gathering Interest
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Jira Cloud team