Dependencies cross project not shown

[Steeve Le Dréau]

Hello,

I'm working between 3 projects : one master (MA) and two others (SL and SM) which are the root dependency.

Let's say I have a user story SL-1 which blocks MA-1

Everything works fine if i'm included into the two projects.

The problem is when a "MA" project only developper opens the MA-1 User strory : the dependency doesn't show up in the dependencies sections. He would have to be a SL project developper too to see the dependency.

This is not an expected behavior, he should at least see that there is a dependency that blocks its US, even if the title is not shown, just the ID and the status would be the minimum to be aware that he can't start this story until SL-1 is done.

Is there a way to fix this problem without joining this user to the SL project ?

Thanks

[Sayed Bares [ServiceRocket] · Accepted solution]

@Steeve Le Dréau welcome to the community!

One way or another you would need to give MA's developers permission to view issues. You don't have to give them a full developer role which allows them to do all sort of things with your Jira issues depending on how this role has been configured in your project permissions.

An easier approach to address this would be granting Browse Projects permission (a permission which allows browsing projects and its issues) to your MA developers instead of adding them one by one into your developer role. Here are some options which you may considers when granting  Browse Projects permission:

• User: you can do it by granting each of users from MA project in Browse Projects SL and SM (NOT recommended, it is very manual).
• Group: You can do it by adding all MA users into a group and then grant that group Browse Projects in SL and SM projects
• Application Access: You can do it by granting Browse Projects to (Jira software application access) this way anyone who has access to your Jira can see issues in SL and SM
• The full list can be found in Add users, groups, or roles to a permission scheme and grant their project permissions

[Steeve Le Dréau]

Hi,

Thanks for your answer, the problem is fixed.

It was a combination of two issues : 

1) Browse project permission that had to be added to the group

2) People who had this problem were into another group (external developers) and I had to include them into Browse Project permissions.

Thanks again ;)