TSheward_SGW Posted May 10, 2018 Share Posted May 10, 2018 Hello, Bit confused as thought this had historically worked fine for basic users, it does work fine for full users so assuming there is a permission/role issue somewhere. When our basic users view a resolved request and click the "It's still broken" button on the self service portal, it adds an update to the timeline but the request doesn't actually reopen. If the basic user has the system default "Basic User Role" and "Self Service User" roles assigned would this be expected behaviour? If so how can we get the request to reopen for them? I have created another role and included 'reopen incidents' and 'reopen service requests' as per thread below and tagged it on to a test user but it doesn't appear to have made any difference. Thanks in advance, Tom Link to comment Share on other sites More sharing options...
Guest Chaz Posted May 10, 2018 Share Posted May 10, 2018 We'll look at making sure the Self Service User Role has the rights that are required, but you can grant the Service Manager Authorised Guest role to get all the rights you need to be able to reopen a Request. Link to comment Share on other sites More sharing options...
TSheward_SGW Posted May 10, 2018 Author Share Posted May 10, 2018 Thanks @Chaz - have added this role to our basic users and now working as expected. Link to comment Share on other sites More sharing options...
P. Nordqvist Posted May 11, 2018 Share Posted May 11, 2018 Perfect, this resolved the issue for us as well. Thanks! Per Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now