Plain-English definitions of every Jira / Forge / PMO term used across the Dashboards Rich Filters product and documentation.
Atlassian Forge
Atlassian’s cloud-only app development platform. Forge apps run inside Atlassian-hosted infrastructure with no external servers, enforced sandboxing, and granular permission scopes. Dashboards Rich Filters is built on Forge.
Atlassian Marketplace
The official storefront where Jira, Confluence and other Atlassian apps are distributed and billed. Marketplace also handles licensing, refunds, and trial periods.
Dashboard gadget
A modular widget displayed inside a Jira Cloud dashboard. Gadgets render their own UI (charts, filters, KPIs) using Jira data, and are added to a dashboard via Edit → Add gadget.
Forge KVS (Key-Value Store)
A per-app, per-installation key-value store provided by Atlassian for small amounts of app-specific persistent data. Dashboards Rich Filters uses it to record a single anonymous installation timestamp.
globalPage
A Forge module type (jira:globalPage) that registers a full-page app entry inside Jira’s top-level Apps menu, separate from dashboard gadgets. Dashboards Rich Filters exposes “Rich Filters Dashboard — KPIs, Burndown & Risk” via this module.
Ishikawa fishbone diagram
A risk-analysis diagram developed by Kaoru Ishikawa in the 1960s that categorises contributing causes of a problem along several branches (commonly People, Process, Quality, Schedule — or the 6M variant: Manpower, Method, Machine, Material, Measurement, Mother-Nature). Dashboards Rich Filters renders one automatically from your Jira backlog.
JQL — Jira Query Language
The SQL-like syntax used to filter Jira issues by field values (project, status, assignee, label, etc.). Example: project = "WEB" AND status = "In Progress" AND assignee = currentUser().
KPI — Key Performance Indicator
A single numeric measure displayed prominently to signal performance. In Dashboards Rich Filters, KPI tiles show totals such as overdue count, completed-this-sprint count, and program health score.
Milestones timeline
A horizontal timeline of Jira versions (or fixVersions) plotted by release date with status colours. Useful for seeing release sequencing at a glance.
Multi-select filter
A filter control that allows selecting more than one value at once. Dashboards Rich Filters provides multi-select filters with type-ahead search across project, status, assignee, component, label, priority and time range. Filters apply to every chart simultaneously.
PMO — Project Management Office
The function inside an organisation responsible for portfolio-level project governance, status reporting and risk management. PMO leads are a primary persona for Dashboards Rich Filters.
Portal (React)
A React technique for rendering a child component into a DOM node outside its parent hierarchy (typically document.body). Dashboards Rich Filters uses React Portals for its filter dropdowns to escape all parent stacking contexts and eliminate z-index conflicts.
Program health score
A composite 0–100 score Dashboards Rich Filters computes from the mix of issue statuses, overdue ratio and blocked ratio across the currently filtered set. Higher is better.
Sprint burndown
A time-series chart comparing the ideal remaining work in a sprint (a linear line from start to end) against the actual remaining work, used to spot scope creep or under-delivery.
Statistics by component
A sortable, paginated table breaking down counts by Jira component (a sub-grouping inside a project, often used to track sub-teams or areas of code).
Stacking context (CSS)
A 3D conceptual layer in CSS rendering that controls which elements paint above which. Mismatched stacking contexts are a frequent source of dropdown / modal bugs. The Smart Filters in Dashboards Rich Filters render through a Portal to bypass stacking issues entirely.