Hi all,
I’ve noticed that Jira sometimes automatically adds new roles or groups to project permission schemes without prior notification.
For example, last week in the Jira Service Management – XX Permission Scheme, a new role called Service Project Customer – Portal Access was added automatically. This means roles like Any Logged-in User or new system roles can unexpectedly gain access to projects.
Is there a way to prevent Jira from automatically assigning new roles/groups to permission schemes without admin approval?
Hi @Dilan Koyunoğlu ,
You can't stop the release of new features, you can only manage it through the release track admin feature: https://support.atlassian.com/organization-administration/docs/what-are-release-tracks/ .
Please flag my reply if useful.
Regards
Hi,
Thank you for your prompt response.
However, I've checked release notes on release tracks. They were no item for adding new role in permission schemes.
How can I control a new feature, if I don't track exactly?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, I understand your point, but you can't have control at this detailed level. It is a common behaviour, new feature will be released and you can't control it such way.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This feature isn't related to the interface or anything else, but it's a setting directly related to the permission scheme. It's really annoying that it's 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.