-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
2
-
5
-
Problem Definition
Unable to view changes made by users in Priorities such as Add, Edit and Delete (located under Issue Attributes)
Suggested Solution
Allow Audit Log to record changes made to Priorities (or Issue Attributes as a whole) by users.
Workaround
Currently, the only way to determine which users have made such changes is by running a grep command on all JIRA access logs using the keywords 'POST' and 'action' (where action is represented by JSP command in the URL that a user clicks to perform an action). An example would be:
jiraurl/secure/admin/AddPriority.jspa
where AddPriority represents a user adding a new Priority in the Issue Attributes.
As such, to search for all POST request to add new Priority, execute the following command in the JIRA-INSTALL-DIR/logs/
grep 'POST' * | grep 'AddPriority'
A line from the output would look like this:
access_log.2017-08-10:10.60.3.225 963x9989x1 admin [10/Aug/2017:16:03:15 +0800] "POST /contextpath/secure/admin/AddPriority.jspa HTTP/1.1" 302 - 13 "http://jiraurl/contextpath/secure/admin/AddPriority.jspa" "Mozilla/5.0 (Macintosh; Intel Mac OS X x_x_x) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/5x.x.x.xx Safari/537.36" "mb84ca"
where the first bold word would be the user name, then followed by the date and time of the request, the POST request and the action done.
If you wish to narrow the output to request by a particular user user, run the following command:
grep 'POST' * | grep 'AddPriority' | grep user
The lines outputted by grep only provides the information as stated above and does not give details as to what has been added, changed or deleted. Such details are not logged by the access logs.
Please note that the above grep command shows all the request attempts in the access logs that have been made, successful or failed.
- duplicates
-
JRASERVER-3157 JIRA Administration Audit trail / notifications
- Closed
-
JRASERVER-42950 Audit Log for Priorities
- Closed