I’m facing a problem.
The scenario is: to see which sprints an issue has been worked on and display the hours spent on the issue.
Therefore, I created a report with issue type and time in the page filters, issue (selected: All hierarchy level members → Issues) and sprint (selected: All hierarchy level members → Sprints) in the Rows, and sprint start date, sprint end date, and hours spent in the Columns.
However, I found that the hours spent did not display the correct values. If I remove the sprint from the Rows, the correct hours spent for each issue are displayed.
I don’t know why and don’t understand the underlying logic. Why does the hours spent not display correctly when the sprint is placed in the Rows?
Can anyone help me?
Here’s an explanation of how the “Hours spent” measure works together with the Sprint dimension:
Hours spent show logged hours during a selected sprint.
Hours should be logged in the following period of a sprint to consider them as logged during the sprint (exact date and time is taken into account):
from the date when the issue was added to the sprint;
to the date when the issue was removed from sprint, or sprint completion date (if the issue was not resolved during the sprint); for issues resolved during the sprint, all hours logged after the sprint is closed also are counted.
eazyBI looks for issue work log entries with “Date started” within the described time period and then sums up all time spent from those work logs. For subtasks, the time period is calculated based on their parent issue data.
In your case, the issue’s logged hours aren’t showing up for the sprint because of the timing of the work log entry. Even though the work log was recorded after the sprint started, its start time was before the issue was added to the sprint (seems that it was manually changed). Since eazyBI uses the work log’s start time to assign hours to a sprint, those hours aren’t counted.
