DFE-Digital / DFE-Digital/compass

Exportable “All services” detailed report (flat extract)

Open
#171 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

Central Ops need a single long-form report that lists every service and all relevant fields in a flat, exportable format (CSV/XLSX). This enables downstream pivoting/filtering for external reporting without having to build bespoke views each time.

User story

As a Central Ops analyst, I want to export a detailed flat list of all services and their reporting fields, so I can pivot/filter the data for different reporting needs and remove anything not required.

Acceptance criteria
  • A new report view exists: All services (detailed export).
  • The view includes one row per service and includes all agreed service/reporting fields (including: division, directorate, portfolio, ownership/delivery, RAG/confidence, path to green, priorities, delivery type, dates, etc.).
  • The view can be exported to CSV (minimum) and ideally XLSX.
  • Export respects the user’s access scope (Central Ops exports everything; divisional viewers export their scope only).
  • Exported files contain stable column headers (suitable for repeated use in pivots).
  • Performance is acceptable for the current number of services (no timeouts / no partial exports).
Tasks
  • Confirm the complete field list for the extract (map to DB fields / computed fields).
  • Build the report query (including taxonomy joins).
  • Add export endpoint/service for CSV (and XLSX if supported).
  • Add basic filters (optional but useful): date range, status, division, directorate.
  • Add audit/telemetry: who exported, when, and what scope.

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 by confirming the complete field list and mapping each item to database or computed fields, including taxonomy joins. Then define the report view and CSV export, with XLSX and filters as applicable. Done means stable headers, one row per service, access-scoped exports, acceptable performance, and audit/telemetry for exports.

Written by the indexing model from the issue text.

Assessment

Domain
backend, data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.