DFE-Digital / DFE-Digital/compass

Portfolio pipeline reporting (governance area vs delivery area)

Open
#174 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
0
Forks
1
Avg merge
1m
Merged PRs (30d)
3

Description

Description

Portfolios (e.g. Families) need reports covering the total pipeline they are responsible for governance of, not only what they deliver. We need a way to capture and report “in portfolio scope” separately from “delivered by”.

User story

As a portfolio team, I want to see reporting for everything in my portfolio pipeline (including items delivered by other areas), so I can manage boards and oversight using a single source of truth.

Acceptance criteria
  • Data model supports two distinct concepts:
    • Delivery owner (who delivers)
    • Portfolio/oversight owner (who governs / reports it)
  • Reporting can filter/group by portfolio/oversight owner independently of delivery owner.
  • A service can appear under a portfolio pipeline even if delivery sits elsewhere.
  • UI labels/guidance avoid confusion between the two concepts.
Tasks
  • Add “Portfolio / oversight area” field to service metadata (single or multi-select as agreed).
  • Update reporting queries and filters.
  • Add a portfolio pipeline report view (summary + drill-down).
  • Add validation/help text in admin/service edit UI.
  • Plan and complete backfill for existing services.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the service metadata and reporting queries and filters, then review the admin/service edit UI requirements. Done means delivery owner and portfolio/oversight owner are distinct, reports can group and filter by portfolio independently, cross-area services appear in portfolio pipelines, labels are clear, and existing services have a planned backfill.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
analytics, full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.