I like the EPIC-Story-Task breakdown.
But JIRA apparently allows me to have EPIC-tasks, why? Why would I used that?
Also curious how people are using Bugs. Why wouldn't a bug be a story? Bug is fixing a deficiency that needs to be tested and has a story and a user behind it?
Hi Edmond,
Jira is just trying to be as flexible as it can, as there are many ways to organize your work.
Some folks would go EPIC-Story-SubTasks and perhaps have a Task assigned to the EPIC to research some potential technical solution.
As far as Bugs, again there is a number of approaches; production bugs vs development bugs, etc... and you can always come up with your own issues types.
This might be a good discussion topic as I'm sure there's thousands of spins on this.
Just my 2cents
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.