Can a permission scheme be created based on a specific auto created subtask?

[Elif Alverson]

Hello,

Is it possible to have permission scheme for a projects which will allow a specific user to have access to one auto created subtask but nothing else? 

Thank you.

[Tessa Tuteleers · Accepted solution]

Hi @Elif Alverson , 

If you look at your permission scheme, you will see that you can give permissions to User custom fields. 

This means if you give the browse project permission to a User custom field (e.g. "Collaborator"), then you can give "per issue" browse rights. 

If you add the user to that field while creating the automatic sub-task, they only have access to that issue. 

You can look more into this here. 
Be aware, given browse permissions to user / group custom fields make the name of the project available for everyone in the instance. -> Bug report here

Hope this helps! 

- Tessa

[Elif Alverson]

@Tessa Tuteleers , I will look into this and let you know. Thank you so much for your quick response. 

[Tessa Tuteleers]

Hi @Elif Alverson , 

did you figure it out? 
If not, let me know! :) 

- Tessa

[Elif Alverson]

Hello @Tessa Tuteleers , could you please confirm if I understand you correctly here? 

1- Add the browse project permissions-->  Potential Collaborator option as it shows below. Is that correct? 

2- This user needs be the assignee of a subtasks if the custom field location matches so that they can work on this subtask and resolve it. Will they able to do that? 

3- What do you mean by " Be aware, given browse permissions to user / group custom fields make the name of the project available for everyone in the instance."? Does that mean this subtask or the project will be visible to project agents or the rest of the company? Please clarify. 

Thank you.

[Tessa Tuteleers]

Hi @Elif Alverson ,

1. & 2 If you need users to be assignee in a JSM project, you need to be aware of a lot of things: 
   1. The user must have a JSM license and must be part of the "Service Project Agent" Role
   2. You must make sure that the "Service Project Agent" Role does not give browse project permissions (otherwise the users will see all issues)
   3. You need to put the "Assignee" field in the browse project permission -> Not the Potential collaborator field
   4. You need to make sure that the user has the assignable user permission
2. See the given link, the Name of the project will become available for all users

Browsing the Permission documentation can give you a more indeth insight how everything works, but I hope this helped a bit.

Cheers,

- Tessa

[Elif Alverson]

@Tessa Tuteleers ,  thank you so much. I get back to you later.