mirror of
https://github.com/empayre/fleet.git
synced 2024-11-06 00:45:19 +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>
768 B
768 B
| name | about | title | labels | assignees |
|---|---|---|---|---|
| 🧩 Sub-task | Specify a sub-task. (Avoid comments. Use only as prescribed.) | ~sub-task |
Related user story
TODO
Task
TODO
Condition of satisfaction
TODO