Extend a report or export with fields the schema already carries
Fields already in the schema, surfaced in an export somebody assembles by hand every month.
The ticket
Add fields the schema already carries to an existing report or export.
Acceptance criteria
- The new fields appear in the output
- A fixture test pins the output shape
- Existing consumers of the export are unaffected
- Empty values render consistently with the other columns
What lands as proof
A fixture test on the exact output shape, which is what protects the consumers already parsing it.
Why teams defer it
- It gets worked around with a manual query, which removes the pressure to build it properly.
- Whoever asks for it needs it once a month, which never clears the bar for a sprint.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: add fields the schema already carries to an existing report or export. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means fixture-based test on the output shape, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.