Reports & dashboard
- The dashboard is personal and shows what to do next.
- Reports show everyone how a project is going.
Neither needs extra input, and both are only as accurate as your issues.
Your dashboard
Open Home in the sidebar. At the top you see your name, the date and, if a sprint is running, which day of it you are on.


The active-sprint card
When a Scrum board has a sprint running, the large dark card shows:
- the sprint's name and goal
- chips for the sprint day, story points completed out of committed, and issues finished out of all issues
- a ring with the progress as a percentage
- avatars of everyone with issues assigned in the sprint
To board opens the board. Without a sprint, the card shows a Kanban overview whose progress counts finished issues instead of points. Without a board, it offers to plan a sprint.
Pin a board
By default the card picks the first running sprint among your projects. Use Customize to pin a fixed board.
The four key figures
Tapping a tile opens the Issues list filtered to exactly those issues.
| Tile | What it counts |
|---|---|
| Today's tasks | Your open issues due today or overdue, ordered by priority. |
| In Progress | Every started issue in scope that is not done and not in the backlog. |
| Backlog | Every issue in scope in Backlog or Open. |
| Done | Every issue in scope in one of your project's resolved states. |
Only the first tile is about you
The other three count the whole team's work across every project on the dashboard.
Today's focus
The list shows the first five issues from Today's tasks, highest priority first. Each row has the type, title, key and, in red, how overdue it is. The thin bar on the right is time spent against the estimate, if there is one.
Tap a row to open the issue over the dashboard. All issues → opens the full list. If nothing is due, Hinata shows a short note.
Project progress
The donut shows the percentage resolved across every project in scope. The legend splits it into Done, In Progress and Backlog, with the total count in the corner. If Backlog is the biggest slice, more is coming in than going out.
Focus time
Only your logged hours: seven bars for the last seven days (today's in amber)
and the total at the top. Week / Month shows the last five calendar
weeks. It reads 0.0 h until work is logged. Time from Git commits is not
included. See Tracking your time.
Budget card
With advanced time tracking a dark card shows the three fullest time budgets in the dashboard's projects as honeycomb cells, each with the time left. A cell opens that budget's history, All opens the Budgets tab of the reports.
Team ranking and Git activity
- Team ranking: the ten people who resolved the most issues in the last 30 days. It is meant light-heartedly and deliberately ignores hours.
- Git activity: recent commits, pull requests and merges from connected repositories. Only shown once Git integration is set up.
Customize
Customize in the top-right starts edit mode.


- The fields "Hero board", "Dashboard data" and "Team ranking" appear above the cards. "Team ranking" picks the teams the ranking counts.
- "Hero board" picks the board for the large card. The default is "Automatic (active sprint)".
- "Dashboard data" sets which projects the key figures, donut and Today's focus count.
- The eye button on a card hides it.


Done saves. The layout belongs to your account, so it also applies on your phone. Without Done, your changes are lost.
Reports
Open Reports in the sidebar, or under More on a phone. With advanced time tracking switched on, this opens Time tracking › Reports on its first tab, Project. Next to it sit Budgets and the time reports such as Summary, Entries and Workload. See Advanced time tracking. Without the module, the project overview is a page of its own.


The overview always shows one project. The project capsule at the top opens a search over every project your team access grants you. Next to it you pick 30 days or 90 days.


Figures
Four tiles at the top: the issues open today, those new in the period, those done in the period and, with advanced time tracking, the time recorded in the period.
How do the open issues develop?
- Honey area: open issues on each day of the period, worked backwards from today's count.
- Dashed line: a straight path from the starting value to zero. It is only a yardstick.
What the shape means
- Flat: as much gets done as comes in.
- Rising: more comes in than gets done. Working faster does not fix that.
- Drop just before the end: issues sat in review or QA and were closed in a batch. Where they got stuck stays hidden.
- Exactly on the line: be suspicious. Real work is uneven.
How does the budget fill?
If the project has a time budget, its tube and forecast sit here. View history opens the curve of recorded hours. See Budgets.
Where do the issues stand? How urgent is the work?


States show as glasses filling in the state's colour, custom states such as In Parking included. A pile-up in a state before done points to a bottleneck. For priority, watch the share: if nearly everything is urgent, triage is due.
Who works on what? Where does the time go?
Issues without an owner are listed under Unassigned. Keep an eye on that row. Time per activity only counts time entries in the period, no time from Git commits.
Count is not effort
Every distribution counts issues. Twelve small bugs weigh more here than a three-week migration. Use the charts to find patterns, and talk about the reasons.
Budgets


With advanced time tracking, the Budgets tab lists every budget you may see, fullest first. Running sprints with a budget sit at the top. Each project card shows the time budget with its forecast, the sum of estimates and, if you may see it, the money budget.
Sprint burndown and velocity live on the board
Sprint metrics are on the board's Insights tab, next to Planning and Active sprint: sprint burndown, velocity across finished sprints, average velocity, scope changes and work breakdown by assignee. See Boards & sprints.
Reading the charts correctly
- Check the time window. The trend and time per activity cover the period you picked, the team ranking 30 days, the distributions all time. That is why they can seem to disagree.
- Check your workflow. If everything sits in one vague In Progress, no report can show detail. Change that in the project settings.
- Look for gaps. Missing bars say as much as tall ones.
- Explain your numbers. "Fourteen issues are In Review because one person does every review" helps more than the number alone.
Exporting a report
Export in the top-right. Each export covers only the project on screen.


- Export as PDF: a printable A4 document with your organisation's name and
logo, the project name, a generated-at timestamp, the total count, the
burndown, every breakdown as a table (including time per activity) and page
numbers. It arrives through the share or save dialog, named like
hinata-report-Website-Relaunch-2026-08-20.pdf. - Export as CSV and Export as JSON: the same numbers as data. The web app downloads them. The desktop and mobile apps copy them to your clipboard and confirm with a toast.
Export right before you present
Every export is a snapshot with its generation time printed on it.
Reports show what you can see
The same visibility rules apply as in the rest of the app. See Projects & teams.
Next steps
- Keep issues in accurate states and give them owners.
- Track your time for accurate effort numbers.
- Get sprint metrics from the Insights tab in Boards & sprints.