-
Notifications
You must be signed in to change notification settings - Fork 1
Define lifecycle model and add follow-up/stale metadata #46
Copy link
Copy link
Open
Labels
sub-issueChild issue tied to a larger feature or implementation track.Child issue tied to a larger feature or implementation track.uxUser experience, interaction design, clarity, and usability improvements.User experience, interaction design, clarity, and usability improvements.workflowReview lifecycle, queue behavior, follow-up state, and review process improvements.Review lifecycle, queue behavior, follow-up state, and review process improvements.
Description
Metadata
Metadata
Assignees
Labels
sub-issueChild issue tied to a larger feature or implementation track.Child issue tied to a larger feature or implementation track.uxUser experience, interaction design, clarity, and usability improvements.User experience, interaction design, clarity, and usability improvements.workflowReview lifecycle, queue behavior, follow-up state, and review process improvements.Review lifecycle, queue behavior, follow-up state, and review process improvements.
Summary
Define a lightweight lifecycle model and add the metadata needed for follow-up and stale-state behavior.
Why
Lifecycle work needs a clear model first or the UI and storage start improvising in different directions. The current issue pack split this across multiple smaller tickets, but the underlying work belongs together. fileciteturn7file5
Scope
In scope:
Out of scope:
Done when