-
Suggestion
-
Resolution: Duplicate
-
None
-
None
-
Jira on demand
Jira Agile has good support for linking issues to Epics; but it doesn't have any support for linking features, improvements, bugs, tasks to Stories. It would be great to have the ability to do this, so that the epic reports roll up from the individual issues, Stories and all.
There are many cases where a story is composed of features, bugs, etc - especially issues in other projects. I get that it's not always desirable to break a story in to smaller parts; but there are times when it is.
- duplicates
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-9809] Ability to link issues to stories and not just epics
John Crim
added a comment - Yes, in our view it would be great to have "story" act like a level between regular issues (features, bugs, improvements, tasks) and epics. Because often features, improvements, tasks are the right granularity for developer assignment, and they're all contributing to the story.
In cases where the story can just be implemented in a few days then all we need are stories and epics. But often the stories are longer and we need to break them up. Subtasks could work, but then we'd end up creating issue types like sub-feature, sub-bug, sub-improvement, etc - and the bigger requirement is that these tasks often span projects, which is not possible with subtasks.
So our ideal hierarchy would be:
Epic
- Story
- Feature
- Improvement
- Bug
- Task
And of course story and epic are both optional.
John Crim
added a comment - Yes, in our view it would be great to have "story" act like a level between regular issues (features, bugs, improvements, tasks) and epics. Because often features, improvements, tasks are the right granularity for developer assignment, and they're all contributing to the story.
In cases where the story can just be implemented in a few days then all we need are stories and epics. But often the stories are longer and we need to break them up. Subtasks could work, but then we'd end up creating issue types like sub-feature, sub-bug, sub-improvement, etc - and the bigger requirement is that these tasks often span projects, which is not possible with subtasks.
So our ideal hierarchy would be:
Epic
Story
Feature
Improvement
Bug
Task
And of course story and epic are both optional. tkotecki this relates to two things:
- multi-level hierarchies - here, the customer might be using "Story" as a level like "Epic"
- repurposing the classification panels on Plan Mode for other "containers"
Thoughts?
Thanks for submitting this issue. We see it as a valid feature request, which has been reported under https://jira.atlassian.com/browse/GHS-9455 (which in turn is related to https://jira.atlassian.com/browse/JRA-4446).
Regards
JIRA Agile Team