Build Actionable Insights with Custom Charts
(Timesheets + Custom Charts)
Custom Charts turns complete worklogs into stakeholder-ready views inside Jira (who logged what, against which accounts, actuals vs. estimates), so leads stop rebuilding the weekly report by hand.
1. Install Custom Charts
Add Custom Charts for Jira from the Atlassian Marketplace. Custom Charts setup guide. Overview videos: building a gadget, integration with Timesheets, customizing reports.
2. Work Logged by Author (Funnel Chart)
See how time is distributed across people. Set Source to your Jira data, set Chart by to Worklog Author, go to Calculate and switch Count to Sum then choose Time Spent, set Chart Type to Funnel, and Save/Insert. Example. (To edit an existing gadget, enter Edit Dashboard mode first, then edit the gadget.)
3. Team Estimates vs. Actuals
Compare planned to logged by person. Set Chart by to Worklog Author; under Calculations open +Open and choose Sum then Time Spent; add a second calculation with + Calculation choosing Sum and Remaining Estimate; title it and set the Time Unit in Display Options; Save/Insert. Example
4. Hours by Customer Account by Month (Tile Chart)
See spend across accounts over time. First create the Customer in Timesheets and link it to a Tempo account (guide). Set Chart by to Account; in Calculate switch to Sum and Time Spent; in the third dropdown select This quarter; in Display Options set Time Unit to Months and Chart Type to Tile. This view needs JQL to scope the source correctly. Example
5. CapEx vs. OpEx (optional, advanced)
If Tempo account categories are set up in Timesheets, use JQL to build segments for hours logged to CapEx and OpEx accounts. Requires account category setup plus JQL; scope as phase 2 if your team is not yet JQL-fluent. See Tracking Time on CapEx for Tax Credits and the video.
6. Time Spent by Tempo Team (optional)
Aggregate hours at the team level to compare effort across squads or departments, using Tempo Teams as the grouping dimension.
7. Share it
Add finished charts to a shared Jira dashboard for team leads, or embed in a Confluence page for wider engineering leadership visibility. See Shared Dashboards Overview.
You'll know it's working when you stop building reports by hand and start reading a dashboard, including in QBRs and leadership reviews.
Surface Capacity Gaps (Planned vs. Actual)
(Timesheets + Capacity Planner)
Comparing planned hours to actual logged hours catches gaps that pass approval, reframing the conversation from "why didn't you log" to "your actuals are well below plan, what happened?"
1. Install Capacity Planner
Add it from the Atlassian Marketplace. Installing Tempo Capacity Planner
2. Plan time for the team
Open Capacity Planner, select the relevant space or sprint, and allocate expected hours per person. Planning time for resources · Video walkthrough
3. Run the Planned vs. Actual report
Capacity Planner, then Planned vs. Actual report. Review variance by team member to see who is significantly over or under plan. Planned vs. Actual reports · Video
4. Set a variance threshold
Flag anyone with more than 30% variance between planned and logged hours for review. Weekly planning produces tighter results than sprint-level. High initial variance is expected, most people underplan, so treat it as a calibration signal.
5. Fold it into the weekly check
Have team leads review Planned vs. Actual alongside submission status each Monday.
You'll know it's working when the variance report flags gaps before period close, catching incomplete logging that approvals alone would miss.