Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Multi team dependencies

Hi Team

Dependencies are the flavour of the week;)


  • Create a multi team  dependency, results in the following screenshot
    Dep-multi-01.pngNote the (Related Dependencies) section
  • We enter negotiations and it is revealed we missed a team,
  • We would like to add the additional team dependency and list it in the Related Dependencies list


  • There is no obvious why in JA to build on the (Related Dependencies) list
  • We have tried:
    • To add the additional team, by updating the dependency, this simply replaces the team with the new team on Save
    • the copy function, this copies the 3 related dependencies and does not build in the list of relationships


  •  How do we add additional related dependencies to the list?




1 answer

1 accepted

1 vote
Answer accepted
Adil Malvankar
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 13, 2020

Hi Darren,


When you create a dependency and select multiple teams, it actually creates dependency for each team. In other words it is not one dependency work item for multiple teams.


You are right,  when you edit the dependency to add new team, it will just replace the team and not give you option to add new one and create new dependency for new team only. 

This could be a bug. Please open support case for this.


Workaround to this one is that you delete all the dependencies created for each team and create a new dependency with all teams.


The related dependencies field just gives you option to open other dependencies(duplicated) created for other teams.

You can just create a new dependency with same contents for the new team you missed. This workaround will not show in related dependencies but as all the other fields are same, you will be able to search and list all on dependencies page.


Hope that helps.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events