nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

giving write access to shared board to users without access to the governing project

Stefan Mueller

Hello there,

the situation is as follows. There are two separate Jira projects, one for each party, as each party has confidential issues.

There are also issues which are resolved in collaboration, preferable even on the sub-task level. There is a project independent board what filters these issues and makes them available to the Jira projects of both parties. This approach enables us to create an issue only in one of the projects and to make it visible to the other one.
The next step is to give the other side also write access to these shared but not owned issues. How can we achieve this?

Thank you

Accepted answers

Petter Gonçalves

Hello Stefan,

Could you please provide us more information about the approach you mentioned below?

There is a project independent board what filters these issues and makes them available to the Jira projects of both parties. This approach enables us to create an issue only in one of the projects and to make it visible to the other one.

I ask this question because even if you share both projects in a single board, you'll still need to provide the users with the Browse Projects permission to allow them to see these issues, however, they would also be able to see the confidential issues of your projects since the permission scheme is applicable to the entire project and not per issue.

Anyway, I understand that:

1 - You would like to share issues of both projects for both teams, but hiding the confidential ones.

2 - You would like to give them the permission to edit the issue on both projects, but avoiding it on the confidential issues as well.

Analyzing your current requests, I think the best option for you would be to:

- Give the browser projects and edit issues permissions on both projects for both teams

- Use the Security Level feature to hide the confidential issues:

Configuring issue-level security

Please, let me know if this is the option you are looking for or if you have any questions about it.

All comments

Petter Gonçalves

Hello Stefan,

Could you please provide us more information about the approach you mentioned below?

There is a project independent board what filters these issues and makes them available to the Jira projects of both parties. This approach enables us to create an issue only in one of the projects and to make it visible to the other one.

Anyway, I understand that:

1 - You would like to share issues of both projects for both teams, but hiding the confidential ones.

2 - You would like to give them the permission to edit the issue on both projects, but avoiding it on the confidential issues as well.

Analyzing your current requests, I think the best option for you would be to:

- Give the browser projects and edit issues permissions on both projects for both teams

- Use the Security Level feature to hide the confidential issues:

Configuring issue-level security

Please, let me know if this is the option you are looking for or if you have any questions about it.

Stefan Mueller

Hello Petterson,
I'm sorry for replying that late.

I read Configuring issue-level security

and look likes that it is possible but haven't understood yet in what detail, in sense of possbile limitation etc.

So I thought a while how to answer

Could you please provide us more information about the approach you mentioned below?

Eventually, I made little drawing hope that illustrates my intentions well enough

Jira task sharing.png

Stefan Mueller

@Petter Gonçalves, is my drawing helping you?

Stefan Mueller

@Petter Gonçalves any input needed?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

issue

jira

jira-server

permission

collaboration