Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-91368

Better error message when an admin without browse permission accesses Features tab in a next-gen project settings

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Suggestion:

      To display an error message when an admin without browse permission accesses the Features tab in a next-gen project settings 

      Expected Behaviour:

      When an Admin who does not have browse permission on private a next-gen project accesses the feature tab it should show them a message: 

      "You must have the browse project permission to view this project features."

      Current Behaviour:

      When an Admin who does not have browse permission on a private next-gen project accesses the feature tab it keeps loading without any errors.

      •  

      Steps to Replicate:

      1. As an administrator access a Private Next-gen project settings that you are not a Member, Admin, or viewer of.
      2. Access the features tab in project settings.

        1. Screenshot 2021-01-22 at 3.19.22 PM.png
          Screenshot 2021-01-22 at 3.19.22 PM.png
          79 kB

            [JRACLOUD-91368] Better error message when an admin without browse permission accesses Features tab in a next-gen project settings

            Anusha Rutnam added a comment -
            Atlassian Update - March 2024

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new features 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!

            Anusha Rutnam added a comment - Atlassian Update - March 2024 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new features 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!

              Unassigned Unassigned
              f8dac69712b5 Eshan Anchan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: