Providing access for specific tasks within one project

Question

Hello everyone!

situation:
There is already working Jira with several projects and many users (over 500). There are projects available for different departments - each his own. Access to projects outside their subdivisions is usually closed.

But exceptions are required.

Example:
There is a secret project for the secret department. And there are employees in other departments who must be added to specific tasks within the secret department. Sometimes two or three for one task. They should not see the rest of the tasks of this project.

And there are several groups of such outsiders.

How to make it so that these outsiders can see only those tasks where they are added by observers, but not see other tasks? And haven't you seen the tasks of other outsiders?

Making it so that only current performers can see is not difficult. But, so that only current observers who were added to a specific task - I could not. Either he does not see the task, or he sees all the tasks.

Is it solvable?

It is not possible to solve the security levels, since this will produce the essence of the security levels in large numbers.

I understand that it is impossible to appoint several people or a group as the current performer. This would easily solve my problem.

Nedviga · Answer

@Leo

Thank you, now I'm trying to implement it.
True, you have to do everything on a new test project. The old secret project has been banned from changing so deeply in terms of security.

Leo_e8op2r · Answer

@Nedviga

I'm trying to summarize the things and see if that can meet your requirement

1. Create new role in system "Read or Other Departments"(something which is meaningful)

2. update project's permission scheme as below

2.1 Browse Projects permission --> add new role along with existing groups/roles

3. Create new field in multiple user picker type(Restrict Access) and configured to your project

4 New Issue Security Scheme with just one level(you can define more levels based on your requirement)

Value                                                            Groups/Roles

Secured (Default)                                <All groups/roles which are all having

access to all tasks>

custom field (Restrict Access)

5. Associate the new scheme to your project

6. Update all existing issues security level to new value(will grant access to all secret dept. group)

7. for TASK-1 if you want to include A  from dept-1 and B from Dept-2. I'll edit Task-1 and update Restrict Access field with those 2 users. which will grant them read access to Task-1

hope this helps

BR,

Leo

Nedviga · Answer

Hello Leo

Using the link that you gave, I still could not figure out how to implement the scheme I needed.

In the picture I drew roughly how it should be. There are many other, not secret, departments. And there are a lot of people from other departments too.

Access to tasks appears often, and then other users can be added there ... Chaos and horror =)

Is it possible to somehow overcome it?