We created an archive project, in Jira Service Desk Server. As part of that Archive project we've removed customers from viewing the portal in our permission scheme. So now we are constantly being prompted with "This service desk project has configuration problems and may not work as expected." when it's configured exactly the way we want it.
Does anyone know a way to stop these messages?
It looks like there are a couple of issues for people looking to also block this message for various reasons:
https://jira.atlassian.com/browse/JSDSERVER-1256
https://jira.atlassian.com/browse/JSDSERVER-3657
Shrug...
Also seems there is a setting to dismiss "non-critical" messages, but we seem to be forcefully elected to continually see critical messages.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hello @Matthew Gaffney .
I think removing "The Service Desk Customer - Portal Access" from the project permission scheme is not advisable.
that is why you are seeing that message. I would suggest removing all the customers in your "users and roles" section of the project settings instead.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@robert Mugabuhamye thank you for the quick response.
We don't have "customers" listed under users and roles. Our "customers" are not members of any group, or any role in our JSD configuration.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This, https://confluence.atlassian.com/adminjiraserver075/resolving-jira-service-desk-permission-errors-935391159.html, does say that Service Desk Customer - portal access needs to have the following permissions or you'll get critical warnings.
What I'm looking for is a way to dismiss the warning since we don't want these permissions in this "Archive" project. At least not at this time. I can understand telling me it's bad, but if I click a box that says dismiss anyway... why isn't that good enough?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I do understand your frustration.
The only solution for your Archive project is to put back the permission but to keep the Service desk customer role empty as you have today.
good luck
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't think we will be changing the permission. The whole point is to keep our customers from seeing these issues at the given time.
We wont want to mirror our active project by having this permission as our end users CAN view the portal and view those issues. We also want to keep our customer request types on issues so that we can still report/query on that value (since we know that this would also remove those issues from the portal).
At the absolute end, if no other options are available, we will just deal with the pop-ups. I've even toyed with the idea of removing my admin rights and create a separate account for making administrative changes (even though this will burn another license for each of our administrators)...
Thanks for the help though. :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.