Tasks are categorized by a Task Type taxonomy.
- Bug
- Epic
- Feature
- Idea
- Investigation
- Issue
- Question
- Refinement
- Task
I created these organically, without thinking too much about what they meant.
Now I'd like to come up with a structure and process that makes sense.
I'm finding that some tickets are expanding, with some discovery but not much resolution.
I'd like to determine appropriate workflows and how different things can be resolved.
What is the outcome for different task types?
Bug
Something broke or doesn't work as intended.
Usually reported by user.
Subtypes: regression, ...
Fields: Impact, severity, upstream, context.
How to document solutions to help others prevent mistakes?
Epic
Major project area, ongoing development.
Often corresponds with milestones, versions.
Feature
Description of how a feature works, who it's for, why it's needed.
Instructions on how to build it, for others to follow.
Result: write project documentation.
Provide a recipe?
Idea
A loose thought on something that could be added or changed.
Likely to turn into another follow up ticket.
Needs feedback on feasibility.
Investigation
Related to bug/issue?
Document findings.
Do we need an analysis type as well?
Issue
Initial report of an issue.
Likely a bug, but could be a new feature.
Not necessarily within the system, could be a new thing they want from it.
Question
Resolution: answer.
May lead to investigation, etc.
Refinement
An improvement on an existing feature.
Task
When it's clear what needs to be done.
Provide instructions.