-
Suggestion
-
Resolution: Unresolved
-
5
-
Summary
The customer requested a cross-portfolio, even an enterprise-wide view of dependencies using the Dependency Maps. This was achievable in the old navigation by selecting multiple portfolios in the configuration bar, but it is not possible in the new navigation.
The users have many cross-portfolio dependencies. This was one of their top 6 Use Cases that led them to purchase Jira Align.
How to Replicate
User 1 is a team member of Program A and Team A within Portfolio A.
User 2 is a part of Team B within Portfolio B.
User 1 and 2 can only see teams in their own portfolio.
If User 1 creates a dependency with Dependent on = Team B and requesting from =Team A, User 2 will not be able to see the dependency at all.
Expected Results
Users can see cross-portfolio dependencies they are being requested on
Actual Results
Users can only see dependencies that are in their existing portfolio
- is related to
-
ACE-5427 You do not have permission to view this issue
-
PS-152545 You do not have permission to view this issue
- is resolved by
-
![[JIRA Server (Bulldog)] Story - Created by Jira Agile - do not edit or delete. Issue type for a user story.](https://bulldog.internal.atlassian.com/images/icons/issuetypes/story.svg "[JIRA Server (Bulldog)] Story - Created by Jira Agile - do not edit or delete. Issue type for a user story.")
JAVOM-5598
You do not have permission to view this issue
- is reviewing
-
- resolves
-
PS-170126 Loading...
[JIRAALIGN-6156] Dependency Map - cross-portfolio view
Unfortunately, losing the ability to view Dependencies across Portfolios/Programs/Teams (as we had in old navigation) means our company is not able to continue to utilize the Dependency functionality–with the OOTB graphics and analysis--in Jira Align, which has, to-date, been one of the major selling points of the tool for us. Hopefully the urgency of my and other companies requiring this enterprise-supporting visibility will be resolved soon, and we'll be able to renew our roll-out of Dependency management for our internal customers. Thank you for your consideration.
All comments
Tracking Dependencies in a large Enterprise would require us to be able to span Portfolios and Programs for greater visibility.
As a note, for Dependency Maps, we currently have different views based on the map.
Dependency Matrix (Grid View) = shows cross-portfolio
Dependency Maps (Wheel View)= shows cross-portfolio
Dependency Trend Analysis (Analytics View) - shows cross-portfolio
Dependency Maps (Team Status) = don't show cross-portfolio
Dependency Maps (Incremental Status) = don't show cross-portfolio
Because we have views that do currently show cross-portfolio, please escalate this to Bug.
This is also an issue for the dependency map that is impacting customers.
Pinned by
Bryan Smith
Unfortunately, losing the ability to view Dependencies across Portfolios/Programs/Teams (as we had in old navigation) means our company is not able to continue to utilize the Dependency functionality–with the OOTB graphics and analysis--in Jira Align, which has, to-date, been one of the major selling points of the tool for us. Hopefully the urgency of my and other companies requiring this enterprise-supporting visibility will be resolved soon, and we'll be able to renew our roll-out of Dependency management for our internal customers. Thank you for your consideration.
@jpenrod@atlassian.com