nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can people view requests if I restrict the request type after they have raised it?

Jovin

If I use the restrict requests functionality like on:

https://support.atlassian.com/jira-service-management-cloud/docs/add-or-remove-restrictions-on-request-types/

Can customers still view requests they've previously raised?

Accepted answers

Jovin

Did some testing on Sandbox and as far as I can tell it looks like existing requests that then become restricted remain viewable by the reporter, approvers & participants.

Test steps:

Logged in as customer (non-Admin)
Raised request type
Switched to admin and restricted the request to _no-one-at-all
Logged into non-admin users for reporter, approver & participant and confirmed visibility of issue

All comments

Marc -Devoteam-

Hi @Jovin

I can't tell you. I have not tried this.

Best to test this on the sandbox instance

Jovin

Did some testing on Sandbox and as far as I can tell it looks like existing requests that then become restricted remain viewable by the reporter, approvers & participants.

Test steps:

Logged in as customer (non-Admin)
Raised request type
Switched to admin and restricted the request to _no-one-at-all
Logged into non-admin users for reporter, approver & participant and confirmed visibility of issue

Jovin

@Marc -Devoteam- Cheers for that, went into sandbox and did some testing using the “log in as user” through the directory. Looks like visibility remains for existing issues, unless the login in as user retains some kind of elevated access (I don’t think so)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management