Dashboards, Filters, and Reporting
What to know
Filters are saved JQL queries; they can be shared with users, groups, or projects, and shared filters can power dashboards and gadgets. Dashboards are collections of gadgets (filter results, pie chart, created vs. resolved, sprint burndown). Gadgets respect the viewer's permissions, so a dashboard may show different data to different users. Reports include burndown, velocity, cumulative flow, and version reports for agile teams. JQL supports operators, functions (e.g., currentUser()), and ORDER BY.
Traps
A common trap: a filter shared with a group does not automatically let viewers see issues they lack permission for. Dashboards do not bypass permissions. Another: editing a shared filter changes every gadget using it. Also, JQL functions like currentUser() make a filter personal even when shared. Watch for "why is my gadget empty" - usually permissions or a filter that returns nothing for the viewer.
Rule of thumb
Share filters, not individual dashboards, and verify with a test user that the gadget shows expected data. Use currentUser() for personal views and explicit JQL for team views.
Worked example
A team dashboard shows no issues for one member. The filter is shared with the team, but the gadget respects permissions. Check that the member can browse the projects in the filter; if not, add the user to the relevant project role rather than changing the filter.