-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
-
None
I have a business critical need to add parent/child hierarchy to JIRA, the 2-3 level thing does not cut it, it simply has no chance of address teams that work with many release streams over many teams. Basically its not supportive of enterprise work.
We looked at the Structure plugin...its useless, yes you can make it work for a hierarchy of issues, but you have to use it in such a convoluted way, that there is no point.
So, we're adding the ability to "split" items recursively (a new issue type Split Child with appropriate links and plugins to support that).
That's all good, works fine, but, when it comes to showing the parent/child structure on the rapid board...blam! no hierarchy.
Ok, so on the left side of the rapid board we can see that Epic is used to "scope" what is seen on the right side.
This suggests a natural "navigator" context, great...is there any chance that we improve Greenhopper and allow us to add another row to the left side where instead of Epic it would show our Parent/Child tree?
A hierarchy navigator would only require that we (the admins) can configure the hierarchy navigator with an issue link type(s) so that it would know how to build a tree, on a given issue.
- duplicates
-
- Gathering Interest
[JSWSERVER-8044] As an admin, I would like to be able to configure a hierarchy navigator with an issue type(s) so that it would know how to build a tree, on a given issue
As I mentioned above, having the Epic navigator on the right side set the scope of everything on the right, is a vary natural (and good) scoping/navigation model.
Now that this is possible, other kinds of navigation should be incorporated. If there was a plugin frame work to allow us to develop our own "navigator" plugin for the rapidboard, we could write one based on hierarchical issues, which we have a critical need for at the enterprise level, because we have (for example) defects that get tracked into multiple releases of a software product, and into different teams who own different releases. So there is naturally a hierarchy.
But you could imagine other kinds of navigation.
What if you want to define your own teams, and navigate by them?
What if you want to define a temporary project and navigate by that?
What if you want to navigate by tag cloud?
...
Many ways you can set the scope from left to right...if you can just give us access via a plugin framework, we can write the plugins ourselves.
Many thanks for reporting this issue. We agree Epic hierarchy is a valid feature request, and it's tracked under https://jira.atlassian.com/browse/GHS-9455 - please watch it for updates. I'm not sure if providing the hierarchy navigator in Plan mode is the best way of exposing this functionality though.
Kind regards
Tom Kotecki
Product Manager, JIRA Agile