(talking Kanban here as we don't use Scrum in my company)
Basically, a subtask has to have it's own denomination. So if you are to make Stories sub-tasks, they won't be available as Tasks anymore. (am I mistaken here?)
Having the same problem as yours :
What we did is (not optimal but works for us)
Another option is the structure plugin, which allows task hierarchies (a view of sorts in MVC paradygm) totally decoupled from the board 'views' (and their models).
If anyone has a good alternative for implementing this sort of "multi-tier Kanban" workflow (of which this article is pretty much the "optimal" implementation) I'd be really interested to hear from them.
At least this sounds like good plugin material ;)
This was close, but it does not do exactly what I want. When I am in PRJ-1 I pull down more acctions and select create sub-task. The only thing I am able to select from is sub-task and technical task.
We have an issue type of "Story" so when I try to add sub-task type "Story" I get an error saying we already have an issue type of "Story".
I have linked the issues but that is about the best I can do right now. Any other ideas.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs