Issue Summary

Depends On filter choices are ONLY available for Teams that the end user (with the Team Member Role) either inherits membership of (via a Portfolio or Program) OR has specific team membership into. The end user cannot filter the Depends On field for Teams listed in that field that the user is not a member of.

Steps to Reproduce

1. Create at least three teams, two in the same Portfolio and Program, and one in a different Portfolio and Program
2. Make sure other Portfolios, Programs and Teams exist that are completely unrelated to the user or the teams being used for the test.
3. Setup a dependency between the 1st and 2nd team in the same program (for a comparison)
4. Setup a dependency between the 1st team and the 3rd team, that is in a different Portfolio / Program
5. Create a user with Team Member Role and ONLY make them a specific member of the 1st and 2nd teams
6. Login as that user
7. Open the Dependency section
8. Set the Configuration Bar to the 1st Team
9. Check that the Depends on field does show rows covering both the 2nd and 3rd Teams
10. Select Apply filter -> Depends On ->Team
11. The drop down will only contain the team names where the user is a member, even though the Depends on field also shows teams they are not members of.
12. Change the filter to Depends On ->Program
13. The Drop-Down now shows a complete list of Programs and not just those they have memberships to. (So shows inconsistent behavior)

Expected Results

Depends on —> Teams filter drop down should either display all Teams OR better still just All Teams that are listed to the user in the unfiltered Depends On field

Actual Results

Depends On —> Teams filter drop down shows ONLY Teams that the user is a member of, irrespective of whether those teams are displayed in the Depends On Field

The two screenshots (from an Atlassian Test Environment) that are added as attachments, show:

• the Depends On -> Teams drop down not displaying ACW-TEAM21 (as they are not a team member)
• the Depends On -> Programs drop down, showing a number of Programs that they are not members of (showing the inconsistency.)

Workaround

Only unsuitable workarounds are available, these being:

Make the user a Member of the Team (or the related Portfolio or Program for that team)

• This is unsuitable as it gives the affected users visibility to areas not related to their role and in the case of large environments (such as that for this customer) increases the admin overheads due to multiple Portfolios, Programs, Teams and Users 

Use the option to sort the Depends On field and then just scroll down to find the teams of interest

• This is unsuitable as the list of teams shown in the field may be large.