Time spent
Report Usage
This bar chart report displays the hours logged by each user over a selected period, showing the distribution of hours spent within each ticket. The Y-axis shows hours spent, and the X-axis lists users with worklogs during that time.
Specific functionality:
To see the number of issues and total time spent by each person, the user can hover over the bar, tooltip will appear.
To quickly change a time segment user can use the date bar swap at the top of the report.
The user is able to open detailed issue view with the time spent on each issue for the specific person by clicking on his bar.
Next to the date bar swap, a dropdown allows temporary period changes without affecting the saved report.
On the Y-axis user can see the number of hours and on the X-axis the user can see the tickets key.
At the top of the report user can see the person`s name and the same date bar swap for changing a time segment.
While hovering the bar, a tooltip appears. It shows the issue summary and time spent on this issue.
The user is able to see all worklogs in the pop-up by clicking on an issue bar.
Setting up a report
The report has 3 tabs of configurations: Data source, Parameters, Description.
Data source & Descriptionurce
This report supports filtering issues by Basic Source, Saved Filter, or JQL query. For full guidance on how to configure your data source and , see the https://grandia-solutions.atlassian.net/wiki/spaces/HUB/pages/551485467/Data+Source+Report+Description?atlOrigin=eyJpIjoiNzc5Mzg3MjlmNjBmNDc1YjkxNjhhMjE3Mjg5YzU1NDAiLCJwIjoiYyJ9
Specific Report Parameters
Allow users to tailor the report to their specific needs and preferences.
The Period field is required. It lets the user select the time unit to customize the displayed users' time logs and issues on which time was spent. By default, it will be set as a Months.
Report Use Cases
✅ See how much time each team member has logged over a selected period.
✅ Visualize the breakdown of time spent per issue by each developer.
✅ Track total effort spent on bugs per team member.