Hi! Firstly I'll say what I really love, then point to how other things would benefit from this.
Epics are great! I love how I can drag and drop tickets into them and they have the same % tracking that sub-tasks get. I also really love the idea of sub-tasks, they make a lot of sense... but they're so annoying to work with after having made them! I want to be able to drag and drop them, move them to another Epic or set them to be a normal task.
Instead of doing all this with subtasks it seems you already have the functionality with Epics. Why not share that with other tasks? Just let us drop one on another to set it as a child. This is such standard functionality in other software!
Tasks and Stories are analogous functionally and JIRA allows us to ascribe meaning to those via Task Labels. Why not also let us simply define the relationship too. Limit the depth of nesting, sure.. but it's clear the Epic is the king. Standard tasks should function like this too. Imagine if we could move a bunch of tickets into an Epic, then drop some of those tickets onto other ones within that Epic to define them as sub-tasks, this would be so much more fluid.
Also, maybe you just throw a popup asking "Convert Sub-task to Task" when we try to drag it out of a ticket into an Epic or Story, or allow us to re-subtask them to other Tasks/Stories, etc.
TLDL: Asking for more fluidity in task type relationships.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.