mirror of
https://github.com/fleetdm/fleet
synced 2026-05-04 22:08:41 +00:00
8fb694f20f
There have been several tickets created for investigation or research purposes like [this one ](https://github.com/fleetdm/fleet/issues/12904) that we don't have a ticket type for within our current three types (`story`, `~sub-task`, and `bug`). This results in the existing scrum item types needing to be misused. I'm adding a fourth type called `timebox` at Mike's request. I'm also including documentation on the usage of this new type. Lastly, I'm proposing we stop calling sub-tasks "unestimated sub-tasks" in the GitHub template because it is confusing and inaccurate. Our documentation states: "Sub-tasks are labeled as `~sub-task` and enable us to break down complex tasks into more detailed and easier-to-estimate work units.". In our estimation sessions, we put point estimates on sub-tasks. The spirit of this statement is that all sub-task points bubble up to their parent story, and the parent story is what matters to the rest of the business. That is clearly defined in our documentation and processes and will not confuse our usage of stories. --------- Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
23 lines
768 B
Markdown
23 lines
768 B
Markdown
---
|
||
name: 🧩 Sub-task
|
||
about: "Specify a sub-task. (Avoid comments. Use only as prescribed.)"
|
||
title: ''
|
||
labels: '~sub-task'
|
||
assignees: ''
|
||
|
||
---
|
||
|
||
## Related user story
|
||
|
||
TODO
|
||
<!-- A sub-task always belongs to exactly one story. The parent user story for this technical sub-task is linked here. Comment on the parent story, not on this sub-task. -->
|
||
|
||
## Task
|
||
|
||
TODO
|
||
<!-- What needs to be done. -->
|
||
|
||
## Condition of satisfaction
|
||
|
||
TODO
|
||
<!-- Describe the conditions of satisfaction that will resolve this issue. The "definition of done". It is always up to contributors to check their own work. But especially keep in mind there is no external quality assurance check for sub-tasks. (Only user stories get automatic external QA. With sub-tasks, it's up to you.) -->
|