Hey,
We have a business project where one person has to create tasks for himself and track them.
At the same time, he should not see the tasks that were created in the service desks in which he will create tasks through the linked issue. Through the help center, he will not create anything.
User history:
Create a task in a business project
Through a task in a business project, he creates a task in a service project
In the service project, he can only see tasks that he himself created through a linked issue or in any other way
Hi @Denis Uschapivsky - This use case is always tricky.
The best way to tackle this is Issue Level Security. You'd need to create a security level that allows your business project user to view those issues. You can leverage automation so that any time a JSM request comes in, it gets automatically assigned that security level.
Hey)
How to create such an automation rule? I'm not a little confused on how to correctly write the conditions for this to work correctly
How to properly configure the security scheme so that it works correctly only with these issues?
I will be very grateful for the answer
Thanks in advance)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The biggest part of this is setting up the Issue Level Security:
https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/
Once you have that in place, you would set up a rule like this:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.