• Hide
      Atlassian Status as at 03 June 2016

      JIRA Software includes a number of features specifically for software teams, such as agile boards, the Release Hub, and developer tools integration. These features give your agile teams additional views, information, and tools to get your teams building world-class software fast. And to use these software features, you need an active JIRA Software license.

      Users with a JIRA Core license can still see many parts of a JIRA Software project, e.g. the issue detail view. However, due to JIRA 7.0 license changes, JIRA Core users won't be able to see or use features specific to JIRA Software.

      Similarly, features that were once available to anonymous users in JIRA Agile or previous versions of JIRA now require an active JIRA Software license as well. Depending on the use-case, e.g. communicating the progress of a release publicly, you can use alternative solutions, such as the JIRA Road Map gadget. Additional solutions may be available in the Atlassian Marketplace.

      For more information about migrating to JIRA 7.0, see the Migration Hub.

      Show
      Atlassian Status as at 03 June 2016 JIRA Software includes a number of features specifically for software teams, such as agile boards , the Release Hub , and developer tools integration . These features give your agile teams additional views, information, and tools to get your teams building world-class software fast. And to use these software features, you need an active JIRA Software license. Users with a JIRA Core license can still see many parts of a JIRA Software project, e.g. the issue detail view. However, due to JIRA 7.0 license changes , JIRA Core users won't be able to see or use features specific to JIRA Software. Similarly, features that were once available to anonymous users in JIRA Agile or previous versions of JIRA now require an active JIRA Software license as well. Depending on the use-case, e.g. communicating the progress of a release publicly, you can use alternative solutions, such as the JIRA Road Map gadget. Additional solutions may be available in the Atlassian Marketplace . For more information about migrating to JIRA 7.0, see the Migration Hub .
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Summary

      Making JIRA Agile board public no longer works in JIRA 7. This was possible in JIRA 6.

      Steps to reproduce the problem

      1. Grant Browse Project permission to Group: anyone in the permission scheme associate to the project
      2. Access the board using URL

      Expected Result

      User should be able to view the board without having to login

      Actual Result

      User is directed to login page, and there is no option to access the board

        1. board.png
          board.png
          110 kB
        2. JiraPublicBoardBug.jpg
          JiraPublicBoardBug.jpg
          51 kB

          Form Name

            [JSWSERVER-13060] Having an option to Make JIRA Agile board public in JIRA 7

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3070259 ] New: JAC Suggestion Workflow 3 [ 3663331 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]

            Dashboard gadged "Days Remaining in Sprint Gadget" not showing any data for anonymous users. I guess it's a consequence of this restriction. Can you please confirm?

            Luís GÓIS added a comment - Dashboard gadged "Days Remaining in Sprint Gadget" not showing any data for anonymous users. I guess it's a consequence of this restriction. Can you please confirm?
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2625781 ] New: JAC Suggestion Workflow [ 3070259 ]

            Samer Odeh added a comment -

            We configured some boards and we would like to join them with some users who have no account on JIRA, and it doesn't make sense to create account for everybody who need only to read the board, as the number of people is too many and they have nothing to do with JIRA except reading the board from time to time. I already logged ticket GHS-130685

            Samer Odeh added a comment - We configured some boards and we would like to join them with some users who have no account on JIRA, and it doesn't make sense to create account for everybody who need only to read the board, as the number of people is too many and they have nothing to do with JIRA except reading the board from time to time. I already logged ticket GHS-130685
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2321142 ] New: Confluence Workflow - Public Facing v4 [ 2625781 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2040408 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2321142 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2029000 ] New: JIRA PM Feature Request Workflow v2 [ 2040408 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 1127644 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2029000 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: affects-server New: affects-cloud affects-server
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server

              Unassigned Unassigned
              azuhra Aqqiela
              Votes:
              20 Vote for this issue
              Watchers:
              36 Start watching this issue

                Created:
                Updated:
                Resolved: