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 doubt that GreenHopper will support this at this point. Usage of structure plugin is an alternative for https://marketplace.atlassian.com/plugins/com.almworks.jira.structure
I see this as a big limitation. It looks to me like there are some legacy architecture issues becasue of Jira. I was using Rally where stories can be nested. It is very easy to define a nested backlog in Rally. Am I wrong in thinking this is a limitation?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I concur with Scott, TFS allows Nesting of Epics as well as User stories (parent / child relationship), in the equivalent of the linked issue field and display accordingly in structure I guess
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
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.
F.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.