Tabs are the building blocks of the report. By default, you have one of each kind. And each one serves its own purpose.
Why: provides a better understanding of the context.
How: by displaying issue trees like Epic > Story > Sub-task. Custom hierarchу levels like Initiatives and Themes from Portfolio are also supported
Read more about the Issue Structure tab.
Why: everyone loves pivot tables when they are done by someone else.
How: allows to see distributions like remaining time per assignee per issue type grouped by project made in just several clicks. Cool, ha?
Read more about the Pivot tab.
Why: get a better understanding of where spent time is invested. Well, compared to Jira default views, it’s not better, it’s just superior.
How: display data from worklogs as a pivot table. The value can’t be changed, it’s always time spent, but you can play around with date range and pivoting options.
Read more about the Worklogs tab.
Why: get something meaningful from the due dates in issues.
How: map Original Estimates per assignee to periods like a month, two weeks, etc. with an option to split period by days.
Read more about the Capacity tab.
Why: if a plan doesn’t have flaws, it’s probably just because you haven’t noticed them yet.
How: a customizable set of markers that highlights possible flaws. May be treated as a fellow project manager, who’ve seen some stuff.
Read more about the Warnings tab.