Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-18076

Warn about assigning "Anyone" group in Global and Project permissions

    XMLWordPrintable

    Details

    • UIS:
      11
    • Support reference count:
      50
    • Fixed in Long Term Support Release/s:
    • Feedback Policy:
      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.

      Description

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

      Assigning anyone to global permissions such as a "Browse user" is a sure way to shoot yourself in the foot inadvertently.

      We make a vague mention of it in the documentation

      • if you wish to grant the permission to non logged-in users, select 'Anyone' (not recommended for production systems). Note that the 'JIRA Users' permission (i.e. permission to log in) cannot be granted to 'Anyone' (i.e. to non logged-in users) since this would be contradictory.

      A worse impact can happen if 'Browse Project' (in Project Permissions page) is misconfigured for 'Anyone'. This may allow public search engine crawlers to index JIRA issues.

      We should add an explicit warning on the Global Permissions and Project Permissions page.

      Alternatively we could update the wording description like was done in JRA-29503. That is, we could change "Anyone" to "Public" (or "Anonymous and JIRA users").

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mrzymski Maciej Rzymski
              Reporter:
              andrew.myers Andrew Myers [Atlassian]
              Votes:
              76 Vote for this issue
              Watchers:
              55 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: