We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-40787

It should be possible to restrict access to the Issue Navigator by anonymous users

XMLWordPrintable

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

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Currently, even if a user is not logged into JIRA, he/she will still be able to access the Issue Navigator using the URL: http://<JIRA_URL>/issues/?jql=/.

      Steps to reproduce:

      1. Setup a JIRA instance.
      2. Try to go to the Issue Navigator URL (for example: http://localhost:8080/issue/?jql=)
      3. Even if you are not logged in, you will still be able to see the issue navigator.

      There are customers who share their filters with everyone, and having the Issue Navigator URL publicly accessible allows for any user to browse those filters and see the filter owner name, for instance.

      Although this is the expected behaviour, it would be helpful to have the possibility of restricting access to the Issue Navigator (e.g. in the General Settings) so that anonymous users are redirected to a login page.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-40787

            It should be possible to restrict access to the Issue Navigator by anonymous users

            XMLWordPrintable

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

                NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

                Currently, even if a user is not logged into JIRA, he/she will still be able to access the Issue Navigator using the URL: http://<JIRA_URL>/issues/?jql=/.

                Steps to reproduce:

                1. Setup a JIRA instance.
                2. Try to go to the Issue Navigator URL (for example: http://localhost:8080/issue/?jql=)
                3. Even if you are not logged in, you will still be able to see the issue navigator.

                There are customers who share their filters with everyone, and having the Issue Navigator URL publicly accessible allows for any user to browse those filters and see the filter owner name, for instance.

                Although this is the expected behaviour, it would be helpful to have the possibility of restricting access to the Issue Navigator (e.g. in the General Settings) so that anonymous users are redirected to a login page.

                        Unassigned Unassigned
                        dconrad Danilo Conrad
                        Votes:
                        34 Vote for this issue
                        Watchers:
                        30 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            dconrad Danilo Conrad
                            Votes:
                            34 Vote for this issue
                            Watchers:
                            30 Start watching this issue

                              Created:
                              Updated: