Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-30848

default issue security not used when security level field hidden (and error message)

XMLWordPrintable

    • Icon: Support Request Support Request
    • Resolution: Handled by Support
    • Icon: Low Low (View bug fix roadmap)
    • None
    • 5.1.8
    • None
    • None

      I have set an issue security scheme for one of our projects.

      There is only one security level (hence, it is the default). (see issue-security1.jpg)

      Upon creating a new issue, that security level is not applied to the issue.

      Trying to associate the security scheme again shows that there are issues that have no security level but it doesn't allow to set the level again. "The project is already associated with this scheme" (see issue-security2.jpg)

      This seems to happen only if the security level field is hidden in the field configuration. (Although it wouldn't be shown to the normal user in any case because lack of permission.)

        1. issue-security1.jpg
          issue-security1.jpg
          38 kB
        2. issue-security2.jpg
          issue-security2.jpg
          41 kB

            [JRASERVER-30848] default issue security not used when security level field hidden (and error message)

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 - Restricted [ 2563553 ] New: Support Request Workflow [ 3436300 ]
            Ignat (Inactive) made changes -
            Workflow Original: JRA workflow with restrictions [ 1650049 ] New: GreenHopper Kanban Workflow 20141014 - Restricted [ 2563553 ]
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-30848 [ JRACLOUD-30848 ]
            Katherine Yabut made changes -
            Workflow Original: classic default workflow with restrictions [ 1529100 ] New: JRA workflow with restrictions [ 1650049 ]
            Owen made changes -
            Workflow Original: classic default workflow [ 661957 ] New: classic default workflow with restrictions [ 1529100 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: classic default workflow [ 452318 ] New: classic default workflow [ 661957 ]

            JM R. added a comment -

            For everyone experiencing the same problem: it is believed that this is related to JRA-27544 and that we have to wait for that one to be fixed.

            JM R. added a comment - For everyone experiencing the same problem: it is believed that this is related to JRA-27544 and that we have to wait for that one to be fixed.
            John Chin made changes -
            Link New: This issue is related to JRA-27544 [ JRA-27544 ]
            vkharisma made changes -
            Resolution New: Handled by Support [ 8 ]
            Status Original: Reopened [ 4 ] New: Closed [ 6 ]

            vkharisma added a comment -

            Hi Roth,

            Unfortunately it is not possible to do so. The company name is an automated field and we use it to manage our issue.

            Thanks,
            Vicky.

            vkharisma added a comment - Hi Roth, Unfortunately it is not possible to do so. The company name is an automated field and we use it to manage our issue. Thanks, Vicky.

              Unassigned Unassigned
              823134ca6b95 JM R.
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: