Issues created by 'Anonymous' user in Jira
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
There are multiple issues with the reporter set as "Anonymous", however, Jira configuration does not allow anonymous access.
Diagnosis
Case 1:
Review User Management if there is a user 'Anonymous' created on LDAP or on the Jira Internal Directory.
Case 2:
The auto-filling reporter field was disabled to prevent Jira from pre-setting the reporter with the current use.
Review the article HowTo disable auto filling reporter field when creating issues and check if the Velocity template reporter-edit-frother.vm located under $JIRA_INSTALLATION_DIRECOTRY/atlassian-jira/WEB-INF/classes/templates/jira/issue/field is commented out. If you edit an issue to change some field, it will reset the Reporter field to Anonymous if you don't fill the Reporter field again.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
...
#** Comment out the lines which pre fill the reporter
#if ($reporterDisplayName)
#set ($username = $textutils.htmlEncode($reporter))
#set ($displayName = $textutils.htmlEncode($reporterDisplayName))
<option selected="selected"
class="current-user"
data-field-text="$displayName"
data-icon="$reporterAvatarUrl"
value="$username">$displayName</option>
#end
*#
...Case 3:
(Working as expected)
The reporter field is not a required field by default and users can leave it empty if they choose to, which leads to the appearance of the "?" Anonymous.
Solution
Case 1:
Deactivate the account 'Anonymous" following the instructions under the "Deactivating users" session in Create, edit, or remove a user documentation.
Case 2 and case 3:
Change the field configuration to make it mandatory, following the documentation Making a field required or optional.
Was this helpful?