Skip to main content
Technology

Consistent, filterable RAG status

A Multi-Team RAG Status Rollout Pattern for Jira

This is an illustrative implementation scenario based on product capabilities, not a report about a named or measured customer deployment.

The Challenge

A multi-team technology organization may collect project health through spreadsheets, slide decks, and recurring status meetings. Common problems include:

  • status definitions that vary between teams;
  • reports that are already stale when they are presented;
  • manual copying of Jira information into a separate reporting format; and
  • difficulty finding the Jira issues behind a red or amber status.

The Solution

A representative Traffic-Lights for Jira rollout could use the following phases.

Phase 1: Define RAG Criteria (Week 1)

Before deploying the field, define observable criteria that teams can apply consistently:

  • Green: On schedule, no blockers, within budget
  • Amber: 5-15% schedule variance, blockers with mitigation plans, or resource risks
  • Red: >15% schedule variance, critical blockers without resolution, or scope changes pending

Phase 2: Team Rollout (Weeks 2-4)

Add a Traffic-Lights custom field to the Jira issue types selected for reporting. Assign an owner and review cadence for each status instead of relying on the field to update itself.

Phase 3: Filtered Views (Week 5)

Create Jira filters and views for each audience:

  1. Team views showing the work items owned by a delivery team.
  2. Program views selecting relevant cross-project issues with JQL.
  3. Management views showing the chosen issues and their traffic-light status in a dashboard gadget.
  4. Confluence pages embedding Jira status where stakeholders consume project context.

What to Validate in a Pilot

  • Confirm which issue types represent the reporting level.
  • Test JQL filters and dashboard access against restricted projects.
  • Check that the gadget's issue list and configured columns answer the intended reporting question.
  • Document who may change the status and what evidence supports each color.
  • Measure preparation and meeting time before and after rollout if the organization wants to quantify the effect.

Expected Operational Effect

A shared RAG field and filtered Jira views reduce copying between tools and make it easier to find the issues behind a reported status. The product does not itself aggregate portfolio metrics or guarantee less meeting time; those outcomes depend on the reporting design and team practices.

Products Used

Want to test this pattern with your Jira projects? Try Traffic-Lights for Jira or contact us to discuss your use case.