Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Fixed
Fix Version/s: 4.9.0
Component/s: None
Labels:
- not-fixed-in-cloud

Feedback Policy:

We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

Description

JIRA Service Desk use case has issue security to protect information via many different levels of security. However, this field is not exposed to the customer when they create a ticket, so the highest level of security must be set by default. Often times this means the user can no longer access their tickets as they don't have access to the highest level of security. The field should be exposed to the user so they can select the appropriate issue level security when creating the ticket.

Attachments

Issue Links

causes

JSDSERVER-7155 Security Level visibility changes after 8.13, upgrade task missing

Closed

is related to

JSDSERVER-6041 Issues do not appear on My Requests if Customer is an Agent who is denied access by the Issues' Security Level

Gathering Impact

resolves

JSDSERVER-4259 Security Level available to be added in the request type field settings

Closed

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

was cloned as: JSDS-663 Loading...

(7 mentioned in, 1 was cloned as)

Activity

People

Assignee:: Unassigned

Reporter:: James E. Hunt [ASRC Federal]

Votes:: 2 Vote for this issue

Watchers:: 7 Start watching this issue

Dates

Created:: 17/May/2017 12:36 AM

Updated:: 24/Mar/2021 5:56 AM

Resolved:: 20/May/2020 8:51 AM

Make issue security field settable by customer