Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-65764

Log changes made to Priorities by users in Audit Log


    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 2
    • 5
    • 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.

      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.


      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:


      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:

      Example of output from grep command

      access_log.2017-08-10: 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.

            Unassigned Unassigned
            jthomas2@atlassian.com Joshua Thomas (Inactive)
            31 Vote for this issue
            23 Start watching this issue