Groom you project

[lakruzz]

• Create a milestone for each feature you prioritized previously
• For each feature brainstorm all potential tasks and mark them as belonging to the milestone you just created.
• As you work, consider if you need to be able to filter some of these in a view; e.g. by category, competence required. If you identify any such need, then create a label to filter on and apply the label to the issue (you might not have that need now - no problem, you can set it later).

---

A note on issues, milestones and labels

GitHub issues¹, milestones and labels are all closely related². They are used extensively in projects too, but they are actually defined in the repos. Consequently draft issues that only exists in the project can not be subject to having labels or belonging to milestones for that to be enabled you must convert the draft to an issue³.

Milestone is not really a god name for this object in GitHub - It implies a time span, but it's merely a container used to model parent/child relations. You could also argue that issues is also not a particular good name, as issues are used to model all kind of work tasks - not just literal "issues".

Footnotes

1. See: GitHub Issues documentation ↩

2. See: Using labels and milestones to track work ↩

3. See: Converting draft issues to issues. ↩