• 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

            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?

            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

            This is an extremely unfortunate move from JIRA Product Owners.  

            As a software development manager, one of the best features to me of the agile process is the improved transparency with the business.

            Requiring business owners to have a license just to see the dashboard deprives me of that benefit.  I don't think JIRA product owners agree with me on the transparency value – another good example is the inability to improve the contrast of the "wallboard" slide shows which are practically unreadable in my bright sunlit office (https://jira.atlassian.com/browse/JRA-38462)

            Very disappointing move.

            Jeremiah Hackler added a comment - This is an extremely unfortunate move from JIRA Product Owners.   As a software development manager, one of the best features to me of the agile process is the improved transparency with the business. Requiring business owners to have a license just to see the dashboard deprives me of that benefit.  I don't think JIRA product owners agree with me on the transparency value – another good example is the inability to improve the contrast of the "wallboard" slide shows which are practically unreadable in my bright sunlit office ( https://jira.atlassian.com/browse/JRA-38462 ) Very disappointing move.

            I am a DevOps within a large organisation. The part of the business that I am in has about 60 software engineers. We are heavily reliant on Atlassian products, with JIRA, Bitbucket and Confluence. I have been administering, configuring and customising JIRA for the last 3 years.

            I am sick to the back teeth of the way that Atlassian operates, especially JIRA. This is just another example. I cannot think of any juistification to remove this functionality. The ability to browse an Agile board as an anonymous user is not (and should never be) a "grey" licensing issue. Thanks to this change our public displays and team boards will no longer function. Why? To extract a few more user licences?

            Having someone from Atlassian (no matter how helpful) suggest a third party product for a function that should be core just doesn't cut the mustard. Time and time again, functionality that should be core to the product is never added because an external provider has a "competing" commercial add-on. And there are examples where this even varies from product to product in Atlassian e.g. an announcement banner - part of JIRA and a paid-for add-on for Bitbucket.

            Don't get me wrong - these products are good. They could, however, be great if Atlassian could sort out their product and commercial strategy.

            Barry Millar added a comment - I am a DevOps within a large organisation. The part of the business that I am in has about 60 software engineers. We are heavily reliant on Atlassian products, with JIRA, Bitbucket and Confluence. I have been administering, configuring and customising JIRA for the last 3 years. I am sick to the back teeth of the way that Atlassian operates, especially JIRA. This is just another example. I cannot think of any juistification to remove this functionality. The ability to browse an Agile board as an anonymous user is not (and should never be) a "grey" licensing issue. Thanks to this change our public displays and team boards will no longer function. Why? To extract a few more user licences? Having someone from Atlassian (no matter how helpful) suggest a third party product for a function that should be core just doesn't cut the mustard. Time and time again, functionality that should be core to the product is never added because an external provider has a "competing" commercial add-on. And there are examples where this even varies from product to product in Atlassian e.g. an announcement banner - part of JIRA and a paid-for add-on for Bitbucket. Don't get me wrong - these products are good. They could, however, be great if Atlassian could sort out their product and commercial strategy.

            lyes.hassaine597653445 I understand your frustration. I'll reach out to our teams internally so we can get a unified message on this. However I honestly think JIRA Core boards could provide the functionality with the right project interaction. Let me work my Support Engineer magic!

            Jose Castro (Inactive) added a comment - lyes.hassaine597653445 I understand your frustration. I'll reach out to our teams internally so we can get a unified message on this. However I honestly think JIRA Core boards could provide the functionality with the right project interaction. Let me work my Support Engineer magic!

            This is a step in the right direction, well done.

            We look forward to seeing this in the server version and hope it doesn't take as long as other labs features (considering this was functionality that has been taken away).

            Still a shame on the lack of product management response on the lack of communication around this issue.

            Lyes Hassaine added a comment - This is a step in the right direction, well done. We look forward to seeing this in the server version and hope it doesn't take as long as other labs features (considering this was functionality that has been taken away). Still a shame on the lack of product management response on the lack of communication around this issue.

            Jose Castro (Inactive) added a comment - - edited

            I just wanted to mention. There is a Atlassian Labs feature that is available for JIRA Core that provides a simple board. I've tested it and you can access it publicly.

            It isn't quite the same as JIRA Software in that you can't really customize much board wise. Yet. This is a developing feature.

            However you can line out your workflow to represent statuses that are intuitive to your anonymous users. While creating advanced workflow function to interact with your JIRA software projects. I'm not saying it's a replacement feature. However if you get creative I think this could work. I'll be monitoring this ticket for use cases that may not work. If you can list your use cases here. I'll will take the time to test the use case and if its not possible create a feature request to move things along in the JIRA Core development process.

            Thanks,
            Ramiro Castro
            Support Engineer
            Atlassian

            Jose Castro (Inactive) added a comment - - edited I just wanted to mention. There is a Atlassian Labs feature that is available for JIRA Core that provides a simple board. I've tested it and you can access it publicly. It isn't quite the same as JIRA Software in that you can't really customize much board wise. Yet. This is a developing feature. However you can line out your workflow to represent statuses that are intuitive to your anonymous users. While creating advanced workflow function to interact with your JIRA software projects. I'm not saying it's a replacement feature. However if you get creative I think this could work. I'll be monitoring this ticket for use cases that may not work. If you can list your use cases here. I'll will take the time to test the use case and if its not possible create a feature request to move things along in the JIRA Core development process. Thanks, Ramiro Castro Support Engineer Atlassian

            Hi All,

            For the OSS projects out there, I did want to highlight the semi-official way of working around this that I posted a while back.

            It's not perfect, but it does seem to function properly with restricted access.

            That said, this is a really silly hoop, and a whole paid account, that you have to jump through.

            Trevor Vaughan added a comment - Hi All, For the OSS projects out there, I did want to highlight the semi-official way of working around this that I posted a while back . It's not perfect, but it does seem to function properly with restricted access. That said, this is a really silly hoop, and a whole paid account, that you have to jump through.

            This is really sad decision that you remove anonymous access option for agile board.
            I'm using JIRA for OSS project under OSS license. Yes, anyone can sign up for our JIRA instance. However still there is need to make agile board public.

            In OSS project, transparency of project management is very important thing for recruiting new contributors.
            Agile board is good interface for new visitor who considering that he/she join or not join to our project. They may think "is project status good or not? how many issues left? Is there jobs I can contribute?" then look into agile board.

            However, you know all visitors do not always want to sign up before deciding to join to the project.
            Of course, Road map gadget is still available for anonymous users as you said. However there are not enough information to consider contributing to the project. In addition, "version" screen is not available for anonymous users. I need to say that functionality of road map gadget is also broken without version screen. Anyway there are too few information showed If road map gadget were works well.

            So how do I show enough information for new visitors who considering to join to our project ?
            Thus, there is opportunity loss for getting new contributors.

            I really want option to make JIRA Agile board public.
            I still believe that Atlassian can do this despite a lot of business difficulties .

            Kakeru Ibuta added a comment - This is really sad decision that you remove anonymous access option for agile board. I'm using JIRA for OSS project under OSS license. Yes, anyone can sign up for our JIRA instance. However still there is need to make agile board public. In OSS project, transparency of project management is very important thing for recruiting new contributors. Agile board is good interface for new visitor who considering that he/she join or not join to our project. They may think "is project status good or not? how many issues left? Is there jobs I can contribute?" then look into agile board. However, you know all visitors do not always want to sign up before deciding to join to the project. Of course, Road map gadget is still available for anonymous users as you said. However there are not enough information to consider contributing to the project. In addition, "version" screen is not available for anonymous users. I need to say that functionality of road map gadget is also broken without version screen. Anyway there are too few information showed If road map gadget were works well. So how do I show enough information for new visitors who considering to join to our project ? Thus, there is opportunity loss for getting new contributors. I really want option to make JIRA Agile board public. I still believe that Atlassian can do this despite a lot of business difficulties .

            +1

            It might be not the right place but here is our story:

            We are unable to keep our users up-2-date with the development of our software.
            It took long enough to bring back the roadmap gadgat to core, but it's useless compared prior 7.x
            The user can only see the date and how many issues have been resolved.
            A click on the version gives us this middle finger response:

            The Activity Stream is still broken for anonymous access: https://jira.atlassian.com/browse/JRA-59335
            The Dashboards button does only display the System Dashboard, I believe this bug was introduced in 7.x as well. (dashboard is public, etc.)

            We can't show the current sprint status on the dashboard either.
            We can't link to the versions, because that is Software as well.

            So our users can currently only look at the "ugly" Issues page, which is for newcomers very messy and not as nice as the agile sprint active board.

            +1 for the question:

            Can you clarify and confirm that if the community does chose to create such a plug-in that allows anonymous users to view issues in a board format, functionality that was present in previous versions, that Atlassian will not remove this plug in from the Atlassian Marketplace?

            Alexander Diller added a comment - +1 It might be not the right place but here is our story: We are unable to keep our users up-2-date with the development of our software. It took long enough to bring back the roadmap gadgat to core, but it's useless compared prior 7.x The user can only see the date and how many issues have been resolved. A click on the version gives us this middle finger response: The Activity Stream is still broken for anonymous access: https://jira.atlassian.com/browse/JRA-59335 The Dashboards button does only display the System Dashboard, I believe this bug was introduced in 7.x as well. (dashboard is public, etc.) We can't show the current sprint status on the dashboard either. We can't link to the versions, because that is Software as well. So our users can currently only look at the "ugly" Issues page, which is for newcomers very messy and not as nice as the agile sprint active board. +1 for the question: Can you clarify and confirm that if the community does chose to create such a plug-in that allows anonymous users to view issues in a board format, functionality that was present in previous versions, that Atlassian will not remove this plug in from the Atlassian Marketplace?

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

                Created:
                Updated:
                Resolved: