Skip to content

Problem: repeated bug causes are never acted on #158

Description

@zolotokrylin

Problem

A contributor filed about fifteen bug retrospectives naming the same cause, no isolated environment for testing webhooks, and cited a tracking issue that did not exist. Nobody reads the retrospectives as a set.

Importance: Medium - retrospectives are written and then nothing consumes them
Urgency: Low - the cost is slow, in repeat bugs
Priority: P4

Solution

A cause named repeatedly becomes tracked work instead of repeating in individual retrospectives. Require each retrospective's prevention step to link a real open issue, and review retrospectives periodically so a recurring cause is promoted to a Goal.

References

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions