Loading Profile...
Meta-stories as containers for multiple stories
We frequently have multiple tasks/stories associated with a larger task that is being split into more granular steps. It's one thing to split a task into 2 or 3 discrete tasks, but it would be great to be able to associate tasks together. Right now we do this by using a title prefix, e.g. "Such and Such: Specific Task", so that we can search for "Such and Such" tasks and associate them together. I don't think labels make sense for this, as these are a set of related tasks within a larger release; they don't have some innate or inherent property, like "splitme". Some kind of task association, or the definition of a meta-task which contains, or from which are derived, multiple granular tasks, would be great.
I’m anticipating
19
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company implemented this idea.
-
Inappropriate?Even something as simple as being able to create dependencies between stories would suffice. Then you could effectively produce a dependency tree and see your most critical path of work to the next release.
1 person thinks
this is one of the best points
-
Inappropriate?Yes please! -
Inappropriate?I'd like to see this feature too, though having dug into all the implications I can see how much it would complicate the system. Right now I'm entering a bunch of stories and trying to decide between labels and title prefixes.
2 people think
this is one of the best points
-
Inappropriate?Strongly agree-- we just had a partner call with one of our contracting companies, and they absolutely need this because they have 10,000+ fine-grained stories for a 5-year $5mil project.
-
Inappropriate?At work we prioritize bugs by placing them under common parents like "High priority bugs" "Low priority bugs" "Customer reported bugs (Top Priority)".
This helps to keep them together and makes it easy to quickly see what has to be done right now.
We are looking at labels to do that, but it's not flexible enough for us.
I’m hopeful
-
Inappropriate?There are several different ideas here, but the original idea from artifactory was about tasks. Tasks will be a part of our next release. You will have to turn them on in your project's settings. -
Inappropriate?I don't think the current implementation of tasks really grasps the idea here. We need entire sub stories. And even maybe sub stories of the sub stories. All with the ability for engineers to drill down and work on pieces of the overall story.
I’m concerned tasks are not enough
