- Time tracking (include on the issue page, either in the description or as a comment)
- Time tracking (include on the issue page, either in the description or as a comment). Each sprint should add up to 60h (30h per week - this allows for meetings/planning to not interfere with the estimates)
- Time estimate, e.g. `/estimate 1d 2h 30m`
- Time spent, e.g. `/spend 4h 15m`
...
...
@@ -151,3 +151,7 @@ Bugs generally start off in the bug triage system (with a `Type::Bug (Triage)` l
-`Triage::Unable to replicate` - we can't reproduce the bug and consequently are unable to resolve it
When the bug is replicable and the issue contains necessary information for a developer to fix it, the bug is taken out of triage by removing the `Type::Bug (Triage)` label and replacing it with either `Type::Bug` or `Type::Regression`. If it's a regression, apply a `Regression::` label so we can identify where things went wrong.
## Epics
Epics will span multiple milestones for a project (#mvp, #review, #release). Avoid using sub epics, as they mess up the roadmap.