Skip to content

Lightweight output persistence for QA/QC of output #95

Description

@john

This could be as simple as dumping JSON output into a Blob so we can later review.

The original PRD specifically said to not do any persistence. We should revisit this--using it for QA/QC is kind of difference, but having learned what we've learned I think it would be useful to revisit more broadly. Even as a user I personally would be frustrated if I could not refer back to the original output. That does not mean we have to make it dangerously easy for users to send out Relais (what's the singular of a Relai report?) without having first vetted them.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions