-
Suggestion
-
Resolution: Unresolved
-
None
-
43
-
7
-
NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.
Hi!
Our company considers JP as a tool to manage and track our business activities at portfolio / department level.
The problem is our 10000+ license JIRA is used both by IT teams and corporate divisons. It means that Hierarchy levels configured (theirs actual names) may pertain to one Line of business and mismatch another another one..
If there was a possibility somehow to define hierarchy levels per plan (or even though per plan's category/template), that would make it much easier.
- is duplicated by
-
- Closed
- relates to
-
- Gathering Interest
- links to
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-24814] Make hierarchy levels configurable per plan
This missing feature is a huge blocker and showstopper for Jira Plans in our organization. Please let me explain the reasons why:
- Projects vary in complexity, and certain projects may require a more detailed or simplified hierarchy. Providing flexibility at the project level allows teams to adapt the hierarchy to the unique demands and intricacies of their project without affecting other projects.
- Introducing a new tool or methodology across an organization can be challenging. Allowing per-project configuration would make it easier for our teams to adopt Advanced Roadmaps (Plans) gradually. Our Teams could transition at their own pace, and project-specific customization facilitates a smoother adoption process.
- Our Teams often have specific reporting and analysis needs based on their project objectives. A per-project configuration would allow our team to define hierarchy levels that align with their reporting requirements, leading to more meaningful insights without affecting the reporting structures of other projects.
- Last but not least: The one and only standard hierarchy does not exist for customers who are using Jira through their entire organization and departments and not only for software development. Where agile and classic methods collide, it is a huge challenge to get the hierarchy levels aligned across all projects.
A must-have feature for our company is the ability to set hierarchy levels required or optional for each project.
Thank you for taking these insights under consideration.
Kind regards,
Chris
Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC
We recently started evaluating Plans after moving to Data Center and while some of our team is excited about the potential, the reality with the global hierarchy is that the value of Plans is limited to only a handful of projects in our organization.
A single global hierarchy is stopping other teams on-boarding to Advanced Plans. I appreciate that some organisations have the same hierarchy, but the system I work on supports multiple organisations and each has their own way of doing things.
Hello there,
is there any progress with this requirement?
Many Thanks
In addition to that it would be cool to have a global setting and a project level setting that overrules is. With that it would be very flexible but still easy to use for the ones following the default hierarchy.
This is blocking adoption within our organization as well. Project based would solve many problems for us.
This is an issue in our organization. We have non-IT teams that have had to shoehorn in IT workflows simply because this feature is not flexible per team. Please fix this.