• Icon: Sub-task Sub-task
    • Resolution: Won't Fix
    • Icon: Low Low
    • None
    • None
    • None

      It would be nice to have the option to configure Security level for Next-Gen projects as on Classic ones.

      Please provide us with more information as to why this feature would be important to your organization and how you plan to use it to inform our R&D efforts, thanks!

            [JSDCLOUD-8713] Add the ability to configure Issue security level

            Atlassian Update - September 22, 2022

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - September 22, 2022 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

            Folks,
            Any updates on this subject?
            thank you,
            Valdemar

            Valdemar Neves added a comment - Folks, Any updates on this subject? thank you, Valdemar

            Joe added a comment -

            We use this to allow certain requests types to be made visible to a subset of the service desk agents–these are typically sensitive issue types such as those involving personnel changes or customer indicated confidential requests.

            Joe added a comment - We use this to allow certain requests types to be made visible to a subset of the service desk agents–these are typically sensitive issue types such as those involving personnel changes or customer indicated confidential requests.

              Unassigned Unassigned
              tbehm@atlassian.com Thiago Behm.
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: