Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-16640

Non-Project Admins can't see Development tools from Project Settings

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Low Low
    • None
    • 7.9.0, 7.6.10
    • Board configuration
    • None

      Summary

      If a user (even JIRA Admins) doesn't have Administer Projects permission, he/she can't see the Development tools link/page from the respective Project Settings.

      Steps to reproduce

      1. Log in as a JIRA Admin who has Administer Projects permission in a project (usually granted to Project role Administrators)
      2. Go to Project Settings of the project -> Ensure Development tools link is still available
      3. Go to Users and roles -> Remove own account from Administrators role -> Refresh the page

      Actual behavior

      The Development tools link mysteriously disappears:

      Manually accessing the page URL gets this misleading error:

      This page is only available to JIRA Software users. If you think you should be a JIRA Software user, you should ask your administrator to give you application access to JIRA Software.

      Expected behavior

      The JIRA Admin should be able to view the link and page contents, assuming that he/she has:

      1. JIRA Software application access
      2. View Development Tools permission

      In case only Project Admins are supposed to view the page, the link should still be there and accessing it displays some more meaningful message.

      Documentation needs updating too: Defining a project - Development tools

      Workaround

      Only Project Admins can see the link and view the page.

        1. error.png
          error.png
          100 kB
        2. nolink.png
          nolink.png
          127 kB

              Unassigned Unassigned
              vdung Andy Nguyen (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: