• 3
    • 6
    • 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.

      Background:

      JIRA show button of 'Agile Boards' when Greenhopper is installed in system. In company's that use JIRA as a tool for customer-developer talk, it's important to control the information that can see customer/client.

      I want to request a new feature for JIRA that allow to show or hide the button 'Agile Board' by group of user. The ideal scenario is that customers don't see this button but developers can see.

          Form Name

            [JSWSERVER-7849] Hide 'Agile Board' by group of users

            +1 archiving would be interesting to some of my colleagues as well

            Klara Zikesova added a comment - +1 archiving would be interesting to some of my colleagues as well

            Just a simple 'Clear Recents' button would do... Then when I visit the boards that I do frequent, they would continue to show as they do now....

            Shaun Grose added a comment - Just a simple 'Clear Recents' button would do... Then when I visit the boards that I do frequent, they would continue to show as they do now....

            Jonathan Hult added a comment - - edited

            ialexeyenko, those 2 workarounds (setting a user to just Jira Core or changing the filter permissions), do work.

            What I would really like is the ability to archive a board. For archiving, the above 2 workarounds don't seem to be the best fit.

            Jonathan Hult added a comment - - edited ialexeyenko , those 2 workarounds (setting a user to just Jira Core or changing the filter permissions), do work. What I would really like is the ability to archive a board. For archiving, the above 2 workarounds don't seem to be the best fit.

            Hi everyone!

            Since JIRA 7.0.0 access to application is based on groups. Now users, who do not have access to JIRA Software can be added to JIRA Core group. Such users do not see the Boards drop-down button.

            Please review this step-by-step instruction how to configure JIRA Core access:

                 

            1. Admin user see applications and groups that control access to them (Note - admin sees the Boards drop-down).
            2. Admin creates a user with only access to JIRA Core application (Note - admin sees the Boards drop-down).
            3. User with access to JIRA Core only does not see the Boards drop-down.

             

            It is also possible to restrict visibility by certain board, keeping the Boards button for all users - see https://confluence.atlassian.com/agile/jira-agile-resources/jira-agile-faq/how-to-restrict-the-access-to-jira-agile-scrum-board for the details.

             

            Does this help addressing your use cases?

            –

            Cheers,
            Ignat
            JIRA Bugmaster.

            Ignat (Inactive) added a comment - Hi everyone! Since JIRA 7.0.0 access to application is based on groups. Now users, who do not have access to JIRA Software can be added to JIRA Core group. Such users do not see the Boards drop-down button. Please review this step-by-step instruction how to configure JIRA Core access:       Admin user see applications and groups that control access to them (Note - admin sees the Boards drop-down). Admin creates a user with only access to JIRA Core application (Note - admin sees the Boards drop-down). User with access to JIRA Core only does not see the Boards drop-down.   It is also possible to restrict visibility by certain board, keeping the Boards button for all users - see https://confluence.atlassian.com/agile/jira-agile-resources/jira-agile-faq/how-to-restrict-the-access-to-jira-agile-scrum-board  for the details.   Does this help addressing your use cases? – Cheers, Ignat JIRA Bugmaster.

            Is there any way we can hide the rapidboard? 

            SS&C Technologies Inc. added a comment - Is there any way we can hide the rapidboard? 

            Did anyone find a way to hide 'Agile Board' button for a subset of users?

            Gajan Umapathy added a comment - Did anyone find a way to hide 'Agile Board' button for a subset of users?

            You can disable the button for everyone by disabling the "Agile Board(greenhopper-rapidboard-operation)" module from JIRA Agile as well.

            Marcus Silveira added a comment - You can disable the button for everyone by disabling the "Agile Board(greenhopper-rapidboard-operation)" module from JIRA Agile as well.

            I know this JIRA is for disabling for a group but here's a work around if you want to disable for everyone:

            1. Go to Manage Add-Ons
            2. Next to "Filter visible add-ons" click on the button to the right and change to "System" (https://<JIRA_URL>/plugins/servlet/upm/manage/system#manage)
            3. Scroll down and click on "JIRA Agile Marketing Plugin"
            4. Click on "9 of 9 modules enabled" to expand the modules
            5. Click the Disable for "Main menu item that will trigger marketing popup when GH is not yet installed"

            David Chou [Intuit] added a comment - I know this JIRA is for disabling for a group but here's a work around if you want to disable for everyone: Go to Manage Add-Ons Next to "Filter visible add-ons" click on the button to the right and change to "System" (https://<JIRA_URL>/plugins/servlet/upm/manage/system#manage) Scroll down and click on "JIRA Agile Marketing Plugin" Click on "9 of 9 modules enabled" to expand the modules Click the Disable for "Main menu item that will trigger marketing popup when GH is not yet installed"

            This also pertains to anonymous access for installations on the WAN. We don't want to advertise what components we have installed on our JIRA setup. It's also unprofessional to have the Agile 'Getting Started' page available to unauthenticated users, who can't do anything with the feature except discover ways to exploit our system.

            Chris Bensler added a comment - This also pertains to anonymous access for installations on the WAN. We don't want to advertise what components we have installed on our JIRA setup. It's also unprofessional to have the Agile 'Getting Started' page available to unauthenticated users, who can't do anything with the feature except discover ways to exploit our system.

            Raven Ng added a comment - - edited

            The agile button should not be visible if the logged in user do not have access to any projects associated with "Agile"

            Raven Ng added a comment - - edited The agile button should not be visible if the logged in user do not have access to any projects associated with "Agile"

              Unassigned Unassigned
              8fe1202e1d3b PiR
              Votes:
              191 Vote for this issue
              Watchers:
              82 Start watching this issue

                Created:
                Updated: