Hi all pros!
Based on this existing bug as below, we encounter a problem.
https://jira.atlassian.com/browse/JSDCLOUD-8167
since we set project permission to reporter & current assignee to see their own issues, our customers can see our these irrelevant portal even these portals are restricted already.
i would like to know whether there is any method that i can keep to let only
reporter & current assignee to see their own issues, and our irrelevant customers will not see these portals.
I've tried to use "issue security scheme", but it doesn't work.
is there any other way to achieve? like using automation ?
Welcome @Veronica Liu
Which project roles do you have for your Browse Projects permission in your JSM project?
Project roles: admin, atlassian-addons-project-access
Reporter, Current assignee, and User custom field value
Service project customer-portal access
the above are the users and project roles we add to browse projects permission
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The request type that is being used to place the requests under the Restrictions, you need to check who is under this option:
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.