Summary

      After the release of Project Types and new Application Access (Core and Software) in JIRA 7, there are two problems to access Release pages for anonymous users:

      1. Anonymous users no longer can see the icon to go to the Releases page of this project, though they strangely can use URL to go to it (if they know it).
      2. When they access this page via URL, clicking any version leads to an unaccessible page (the version hub for that version)

      This is probably because development features are now only visible to Software users. However, this is highly inconsistent as an icon to an accessible page is gone, and once we manage to access the page, the links in it are not accessible.

      Also, shouldn't public projects allow access to these pages to anonymous users?

      Steps to Reproduce

      1. Create a public software project (change Permission Scheme to add 'anyone' to the 'Browse Projects' permission)
      2. Access the project as an anonymous user (not logged in)
      3. In the project's left menu, the releases icon is not visible (problem 1):
      4. Since navigating to it is not possible, copy the URL to it and paste it (replace instance and project key):
        https://instance.atlassian.net/projects/PROJECTKEY?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page
        
        • Now we can see the page we couldn't access before
      5. Clicking a version leads to a page like this (problem 2):

      It reads:

      Sorry, you can't view this page
      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 Results

      1. All these pages are accessible (as this is a public project)
        • The icon is visible
        • The link to the version lead to an accessible page

      Actual Results

      The ones described in the Steps to Reproduce.

      Notes

      Also, the documentation is not reflecting these changes. What should public project show now to anonymous users? Only JIRA Core features or should it include JIRA Software?

      Workaround

      None so far.

        1. error.png
          error.png
          76 kB
        2. icon_gone.png
          icon_gone.png
          47 kB

          Form Name

            [JSWSERVER-12827] Access to Release Page on Public Projects

            This does not appear to be fixed. Here's a URL to our publicly open PR tracker project - https://openehr.atlassian.net/projects/SPECPR/versions/10061

            Our community can't see these release pages without being logged in and using a licence.

            Thomas Beale added a comment - This does not appear to be fixed. Here's a URL to our publicly open PR tracker project - https://openehr.atlassian.net/projects/SPECPR/versions/10061 Our community can't see these release pages without being logged in and using a licence.

            Hello,

            I'm still landing on the screen mentioned on step 5 (steps to reproduce)

            I'm using a Service Desk project on Jira cloud. I'm an admin, none of the other admins/users in my company can access this page.

            Please advice,

            Thanks!

            Nelson Moreno added a comment - Hello, I'm still landing on the screen mentioned on step 5 (steps to reproduce) I'm using a Service Desk project on Jira cloud. I'm an admin, none of the other admins/users in my company can access this page. Please advice, Thanks!
            Bugfix Automation Bot made changes -
            Minimum Version New: 7
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2853920 ] New: JAC Bug Workflow v3 [ 2937379 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2546097 ] New: JAC Bug Workflow v2 [ 2853920 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1552014 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2546097 ]

            Kovah added a comment - - edited

            So it is 2018 now and this is still not fixed?!

            Is it that hard to add a new permission "View Releases" in the permission scheme? I just don't understand this. And no, the gadget is not a replacement at all.

            Kovah added a comment - - edited So it is 2018 now and this is still not fixed?! Is it that hard to add a new permission "View Releases" in the permission scheme? I just don't understand this. And no, the gadget is not a replacement at all.
            Martin (Inactive) made changes -
            Assignee Original: Martin [ mjopson ]

            Claudio Weiler added a comment - - edited

            Road Map gadget is NOT a replacement for the releases page. And it links to releases page!!!!

            Releases(versions) pages was visible before JIRA includes Agile concepts by default.

            Any software project has the releases pages, it does not required a board.

            Anonymous user can search issues and filter by version.

            I really see a big lack of logic here. You can monetize JIRA without making your users of fools.

            Claudio Weiler added a comment - - edited Road Map gadget is NOT a replacement for the releases page. And it links to releases page!!!! Releases(versions) pages was visible before JIRA includes Agile concepts by default. Any software project has the releases pages, it does not required a board. Anonymous user can search issues and filter by version. I really see a big lack of logic here. You can monetize JIRA without making your users of fools.
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: fixme warranty New: affects-server fixme warranty

              Unassigned Unassigned
              jsilveira Jaime S
              Affected customers:
              2 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: