Dashboards, filters, and reporting for projects
Filters are saved JQL queries. They can be favourited, shared with a project, a group or everyone, and subscribed to for scheduled email delivery. Because boards, gadgets and many reports are built on filters, filter sharing is a common source of “it works for me” problems: a gadget renders with the viewer's permissions applied to the underlying filter, so an unshared filter shows an empty or error state to everyone else.
Dashboards are collections of gadgets with a layout and a sharing setting. Sharing a dashboard does not share the filters its gadgets depend on; both must be accessible to the viewer. Reports split into board reports (burndown, sprint report, velocity, cumulative flow, control chart, epic report) and project reports (created vs resolved, version report, time tracking). Burndown compares remaining estimate or story points against time in a sprint; velocity averages completed work across sprints; cumulative flow exposes bottlenecks by showing issue counts per status over time.
Traps: expecting a sprint report before a sprint is completed; assuming a dashboard shared to a group shares gadget data; confusing created-vs-resolved (inflow and outflow trend) with cumulative flow; and forgetting that report accuracy depends on transitions actually setting resolution and on consistent estimation.
Rule of thumb: any empty-gadget or missing-data question should be answered by checking filter sharing first, dashboard sharing second, and project permissions third.