How do I set up access in Jira so that only the right people can see the issue?

Question

CVS

Gentlemen, I hope for your help. I myself could not figure it out for an hour and a half, but I did not find it in the documentation.

It is necessary to set up access to tasks in Jira in such a way that you can immediately select those who see it and can participate when creating a task. At the same time, all others should not see this task.

An example of such a scenario:
There are 5 people in my Jira: Misha, Vanya, Petya, Sveta and me.
I want to organize a party. I create a task - Throw a cool party.
I add Misha and Vanya to it, as they will help me.
I won't add Petya and Sveta and I don't want them to see this task.
In the case of Petya, I don’t want him to know about the party at all, since he starts to get into a fight when he drinks, so I don’t invite him at all.
And for Sveta in this task, I create a subtask - Invite girlfriends.
But I know that if she fails to invite her girlfriends, then she herself will not come.
In this case, Misha, Vanya and I will order a stripper, but I don't want Sveta to know about it, so I didn't include her in the main task.

I hope I managed to explain the essence of the access rights that I need.

I could only find the ability to set the visibility of a task only at the level of user groups, not specific people. It seems there is a so-called. Security Scheme, where you can create an access level for an individual. But I didn't figure out how to use this feature.

Answer 1

For tasks, make a field with the “list of users” type, I don’t remember exactly what the type is called. And in Permission Schemes, select the visibility of the task only to the author and those who are listed in this field. If you need more details, I can. But in general - everything is simple, you have to figure it out with a pinch. The main thing here is the field in which there will be usernames.

Answer 2

Oh-oh-oh, this is a complicated topic :)
I will describe my scheme, where I distribute the rights to users according to the project.
Go to Administration -> Issues -> Permission Schemes -> Default Permission Scheme -> Edit Permissions
Replace “Users” everywhere with “Project Role (Users)”
Then go to Administration -> User Management -> Groups
Create your own group there (by name project, for example, "ProjectX")
Now go to Administration -> Projects -> each project -> Administration -> Roles.
In the "Users" line in the "Groups" column, replace "Users" with the group that we created specifically for this project (for example, "ProjectX").
Also in the line "Browse Projects" add the second rule - "Group (administrators)".
Now go to Administration -> User Management -> Users.
And we add the necessary users to the newly created group (in our example, "ProjectX").
Now newly registered users will not have access to anything but the empty Dashboard, in order for the user to gain access to the project, he must be added to the appropriate group.
Maybe I missed something, but it seems not.
There will be questions - ask :)

Answer 3

Basically, the main trouble is to come up with a Permission Scheme for a project that would satisfy your needs in the long run. And to make it so that later some individual users, or groups of users could do something in the project, or could not - the point is, tick the project roles from the table of user project roles (if we are talking about a specific user), and / or add a newly created group (if we are talking about assigning the same permissions to several users - in a specific project) to the Permission Scheme. Very comfortably.
Now, if there was still a thing that allows you to select several users and add
several users at once - project roles, for different projects ...
it would be generally relish - does anyone know if there is such a thing?
Even as a plugin...

Answer 4

How to add a project to Permission Schemes?