How to dismiss 'Resolve Permission Scheme Error'

Question

In Resolve permission scheme errors in Jira Service Management it is stated that we can dismiss the warning in case we do not want to use the default permission scheme which is correct. But only full jira administrators do see the 'Dismiss this warning' link and the 'Upgrade permission scheme' button.

The pop up above has the 'Dismiss this warning' link which allows the system administrator to get rid of the pop up. Next time he accesses the project the warning will not pop up anymore.

Project administrators and other backend users with less access rights do not see those options and so cannot dismiss this warning for their accounts and it gets displayed every time they access the project.

The pop up above does not have the 'Dismiss this warning' link so the user cannot get rid of the warning. But will see it next time again.

Is there a way to dismiss this warning for every user? Since we do not want to use the default permission scheme and all those permissions it is quite annoying to 'x' this warning every time.

Xavier Tang · Answer

The warning is not appropriate in our case. For example, we don't want give the permission right for a Servicedesk Team to delete a ticket according to our organizational process. Only a project admin could do it. This does not block the work. But, the warning disurbs all agents.

Emy Daly · Answer

We were in a similar boat and I found this article useful for our Jira configuration. Resolving Jira Service Desk permission errors.

While Jira Administrators will still have to dismiss the error, at least that is a one time occurrence. The setting described in the article prevents the warning from displaying to the Project Administrators.

Nic Brough -Adaptavist- · Answer

Welcome to the Atlassian Community!

Yes, this error is only dismissable by system administrators, as only system admins are expected to be able to leave projects in a non-working state!

What you'll need to do is correct the permissions, allowing the project to work.  This doesn't mean just using the default scheme, you can still craft your own, but there are a couple of things that you can do that will break the permissions.  Pay close attention to how the default scheme handles customers and agents.