Documentation for JIRA 6.4. Not using this? See below:
(JIRA 6.3.x documentation | JIRA Cloud documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

JIRA can be configured to allow users to create issues without having logged into JIRA. There are two related actions:

  1. Allowing users to browse and search issues in the project without logging in.
  2. Allowing users to create issues in that project without logging in.

These can be achieved by adding the Anyone group to the Browse Project and Create Issue permissions in the permission scheme for the project. Additionally, Reporter, in the project's field configuration scheme, must be set as optional.

Any issue created by a user who is not logged in will display 'Anonymous' for the reporter of the issue.

  • No labels


  1. Is the e-mail of the anonymous user stored?

    Will he/she be informed if the bug has been fixed or somebody commented on it?

    Thanks in advance,


  2. Anonymous

    does an anonymous user count as a "user"

    1. Not really,
      I rather think about a default reporter.

      In our setup every one (not a real jira user, thus anonymous user) should be able to report issues. He/She will be mapped to a standard user (default-reporter).

      My question is: will the e-mail of an arbitrary issue reporter be stored, and will he/she be able to recieve replies and comments regarding his/her report.

      Best regards, m.

  3. Anonymous

    how do you set the default reporter?

  4. How to verify Anonymous user ? Email/Mobile Verification available in JIRA ?

  5. Anonymous

    How can Anonymous user report issues. What are the different steps ?


  6. Anonymous reporters wont  receive notifications as there is no user linked to the issue created, and so JIRA won't know where to send notifications to. Only JIRA users may receive notifications.

    With JIRA Service Desk you can follow the process with customers and send notifications without using JIRA user licenses.

    For anyone interested: to restrict access to some issues but allowing other issues to be publicly accesible see Using Permissions to allow anonymous issue creation and Issue Level Security to restrict issue access