-
Notifications
You must be signed in to change notification settings - Fork 72
Backlog #5
Copy link
Copy link
Labels
backlogTo organize the backlog into a hierarchy. Should never be closed, no assignees, no milestones.To organize the backlog into a hierarchy. Should never be closed, no assignees, no milestones.
Description
Metadata
Metadata
Assignees
Labels
backlogTo organize the backlog into a hierarchy. Should never be closed, no assignees, no milestones.To organize the backlog into a hierarchy. Should never be closed, no assignees, no milestones.
Type
Fields
Give feedbackNo fields configured for Plan.
Borrow ideas/docs from
Note
Many issues have recently been closed as "not planned", not because they were truly not planned, but because they had become stale, which made the current task scope too broad and unwieldy. Once there is enough time to return to "not planned" tasks, it would be great to do so.
Given this, please always search for existing issues, including closed issues, before opening a new one. Even if they are closed, reopen them and proceed with the work.
All issues closed as "not planned" MUST STAY in the tree-like issue Backlog.