It looks to me that curently we have the ability to define epics and a set of user stories under it. For large complex products this is not sufficent. Will GreenHoppwer ever support multiple levels of nested stories?
If i am incorrect in this assumption, please let me know how I can handle multiple nested stories.
I think it is a trade off between simplicity and features. And in most cases, if the project requires to be maintained and controlled by levels more than three, it might not be scrum and agile anymore, but the traditional project management fit into 'scrum ways of working'. No offence meant, just my opinion.
There's no infinite nesting levels by default in Jira. Only Task/Epic->sub task. You can use relationships between tasks elements to nest, but then you would only retrieve your tasks thru search. Maybe you should have a look to Structure plugin.
Well, it depends on why you have to nest. Jira offers the possibility to use componant or version fields to segregate issues. You can also link issues between themselves, and then there is not limit.
A use case would be nice to find best solution for you.
I also view JIRA's limited hierarchy as an unfortunate limitation. This limitation is similar to the old 'tasks may only have one level of sub-tasks' issue, which has been around forever.
I, for one, would like to see JIRA allow arbitrary levels of nesting.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hey everyone! My name is Natalie and I'm an editor of the Atlassian Blog and I've got a question for you: What's your favorite quote about teamwork? We've compiled a list here, along with...
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