-
Suggestion
-
Resolution: Done
-
211
-
30
-
Hello everyone,
Thank you for your interest in this issue.
As part of Jira Service Management Data Center 10.1, we have introduced this feature. This enhancement enables admins to set restrictions on request types, allowing control over who can submit specific requests.
Please refer to our documentation to learn how to create restricted request types.
Kind regards,
Divyanshi
Jira Service Management, Data Center
NOTE: This suggestion is for Jira Service Management Data Center. Using Jira Service Management Cloud? See the corresponding suggestion.
During the listing of the request types, you might want to have a task called "Terminate Employee", but you don't want people who don't have that ability to be able to submit that type of ticket. With a little security on Request Types, this could be solved.
Previous ticket title: User(s)/Group(s)/Roles security on creating certain "Request Types"
- is duplicated by
-
JSDSERVER-965 As an admin I want to be able restrict users to certain request types or request type groups in the Customer Portal
- Closed
-
JSDSERVER-1050 Restrict access to Request Types within one Portal
- Closed
-
JSDSERVER-1634 One Customer Portal with Permission Scheme for Request Type Access (Forms) level
- Closed
- relates to
-
JSDCLOUD-195 Ability to restrict ticket creation for certain "Request Types"
- Closed
- addresses
-
ENT-1441 Failed to load
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
[JSDSERVER-195] Ability to restrict ticket creation for certain "Request Types"
Remote Link | New: This issue links to "ENT-1441 (Jira)" [ 993528 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 982850 ] |
Resolution | New: Done [ 17 ] | |
Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |
Status | Original: Under Consideration [ 11774 ] | New: In Progress [ 3 ] |
Assignee | New: Divyanshi [ dvashist ] |
Fix Version/s | New: 10.1.0 [ 109015 ] |
Description |
Original:
{panel:bgColor=#e7f4fa}
*NOTE:* This suggestion is for {*}Jira Service Management Data Center{*}. Using {*}Jira Service Management Cloud{*}? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-195]. {panel} During the listing of the request types, you might want to have a task called "Terminate Employee", but you don't want people who don't have that ability to be able to submit that type of ticket. With a little security on Request Types, this could be solved. ---- {*}Previous ticket title{*}: User(s)/Group(s)/Roles security on creating certain "Request Types" |
New:
{panel:title=Atlassian Update – 4 November 2024|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff}
Hello everyone, Thank you for your interest in this issue. As part of [Jira Service Management Data Center 10.1|https://confluence.atlassian.com/servicemanagement/jira-service-management-10-1-x-release-notes-1417150501.html], we have introduced this feature. This enhancement enables admins to set restrictions on request types, allowing control over who can submit specific requests. Please refer to our documentation to [learn how to create restricted request types|https://confluence.atlassian.com/servicemanagementserver/restricted-request-types-1453424836.html]. Kind regards, Divyanshi Jira Service Management, Data Center {panel} {panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for {*}Jira Service Management Data Center{*}. Using {*}Jira Service Management Cloud{*}? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-195]. {panel} During the listing of the request types, you might want to have a task called "Terminate Employee", but you don't want people who don't have that ability to be able to submit that type of ticket. With a little security on Request Types, this could be solved. ---- {*}Previous ticket title{*}: User(s)/Group(s)/Roles security on creating certain "Request Types" |
UIS | Original: 253 | New: 211 |
UIS | Original: 211 | New: 253 |