Reporting controls

Configuration & reporting profile

Tune StatusDeck reporting thresholds and visibility for the way your Jira teams measure delivery.

StatusDeck for Jira CloudLast updated: 3 September 2026

Configuration scope

StatusDeck stores reporting settings in Atlassian-hosted Forge storage using the installation, project and board/reporting context. Settings are applied when reports for that context are generated.

Estimation basis

StatusDeck can use the board/default estimation configuration or an explicit reporting override. Supported choices exposed by the current configuration include issue count, Original Estimate and eligible numeric Jira fields.

RAG thresholds

Administrators/users can tune the reporting profile instead of relying on one universal threshold. Current controls include:

  • Green completion percentage
  • Amber completion percentage
  • Amber and Red unresolved-defect thresholds
  • Amber and Red overdue-item thresholds
  • Minimum Remaining Estimate coverage

Readiness rules

Readiness configuration can include estimate, assignee and Sprint-goal requirements, optional due-date requirements, maximum next-Sprint velocity load, minimum Acceptance Criteria coverage and an Acceptance Criteria field configuration.

KPI visibility and accessibility

The reporting profile can keep or hide native StatusDeck KPIs and can include Custom Jira Insights. Accessibility options include showing status text and using patterns alongside colour where supported.

Validation

StatusDeck validates related thresholds before saving—for example, Amber completion cannot exceed Green completion, and Amber defect/overdue thresholds cannot exceed their Red thresholds.

Documentation baseline: 3 September 2026. This documentation describes the current submitted StatusDeck capability set and is updated when material product, permission, storage or security behaviour changes.