Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-4259

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

XMLWordPrintable

      NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.

      Summary

      Security Level field is available to be added in the Request types field configuration in Service Desk.

      Environment

      JIRA Cloud 1000.305.0
      JIRA Service Desk Application - 3.3.0-OD-1000.259.0

      Steps to Reproduce

      1. Create a new Issue Security configuration in your project settings
      2. Go to your Project settings > Request types > Edit fields > Add a field

      Expected Results

      Security Level is an unsupported field and should not be available to be added as stated in the product documentation: Configuring request types and workflows

      Actual Results

      The field is available to be added and will show in the Hidden section where you can add a preset value. This value may be reset upon instance restart.

          Form Name

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

            Bartosz Ornatowski added a comment -

            We have made the Security Level field available in Customer Portal in 4.9.0 release. Please refer to the release notes: https://confluence.atlassian.com/servicemanagement/jira-service-desk-4-9-x-release-notes-1005326200.html

            Bartosz Ornatowski added a comment - We have made the Security Level field available in Customer Portal in 4.9.0 release. Please refer to the release notes:  https://confluence.atlassian.com/servicemanagement/jira-service-desk-4-9-x-release-notes-1005326200.html

            elkrivertom added a comment -

            I stumbled upon this issue going through documentation and testing JSD out for my ACP-400 exam. I actually found the feature to be helpful to have as a hidden field.

            Example - I can create an issue security scheme where I have multiple levels of security. I can then set the security level automatically, at the request type rather than doing it else where and have the option for it to differ based on request type.

            I would prefer if we leave the issue as is and update the documentation.

            Tom 

            elkrivertom added a comment - I stumbled upon this issue going through documentation and testing JSD out for my ACP-400 exam. I actually found the feature to be helpful to have as a hidden field. Example - I can create an issue security scheme where I have multiple levels of security. I can then set the security level automatically, at the request type rather than doing it else where and have the option for it to differ based on request type. I would prefer if we leave the issue as is and update the documentation. Tom 

            Dirk Festerling added a comment -

            It would be great if _Security Level _would be available as a hidden field instead!

            We have a scenario here where certatin issues are supossed to be visible only for some of the agents. Setting up a separate request type for them an assigning the needed security level automatically would be a great feature for this.

            BR
            Dirk

            Dirk Festerling added a comment - It would be great if _Security Level _would be available as a hidden field instead! We have a scenario here where certatin issues are supossed to be visible only for some of the agents. Setting up a separate request type for them an assigning the needed security level automatically would be a great feature for this. BR Dirk

              bornatowski Bartosz Ornatowski
              malonso@atlassian.com Miguel Alonso
              Affected customers:
              7 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: