$customHeader
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Currently in audit log entries are placed when:

  • teams are:
    • created,
    • updated,
    • user is added to team,
    • user is removed from team,
    • group is added to team,
    • group is removed from team,
  • holiday scheme is:
    • created,
    • copied (duplicated),
    • updated,
    • deleted,
    • holiday is added,
    • holiday is updated,
    • user is assigned to scheme,
  • workweek scheme is:
    • created,
    • updated,
    • deleted,
    • user is assigned to scheme.

(info) Currently we work to add more audit logging and it includes: configuration, vacation types and vacation days logging.


To access it, follow the below presented steps ( you need to be logged in as Jira administrator):

  1. Open Jira Administration menu;
  2. Access "System";
  3. Click on "Audit Log".


Directly after doing so you will spot a table-like form with entries, similar like the ones presented below and static elements that are (numbers on below graphic are tied with listed ones):

  1. filter field with instant search result(s) possibility (content included in columns numbered from 8 to 11 can be found here in real time when typed into it);
  2. Find all logs within particular time frame (days in calendar);
  3. Find logs tied with particular user - an individual that you look for must be present in "Author" (8), or/and "Object" (11) columns;
  4. Find logs within particular project (can be useful if you have more than one VACMAN project present)
  5. "Export" button - upon clicking on it you are to be presented with a prompt, similar like a one presented below:

(info) Number of displayed events is dependent of how many of it is present in current display. If filtering is used, then you can limit a number of events to export and do not export everything to get less clutter.

After clicking "export", log is presented to be saved locally as an archived (.zip) file.

6. More menu contains additional options:

• "Audit Log Settings":

Here "Retention period" of gathered log can be set to kept for: unlimited period of time (set by default), 1 month, 3 months, or 6 months.

(info) Log size increase proportional to passed time can be expected, especially significant and visible if unlimited retention period is set.


If external user directory i.e. LDAP events are of no point of interest to you feel free to tick "Hide external user directory" and press save.


• "Audit Log Documentation" - hyperlink to https://confluence.atlassian.com/adminjiraserver/auditing-in-jira-applications-938847740.html where more information about auditing in Jira applications can be found.


7. Column "Date" contains exact date of an occurred event that was logged;

8. Column "Author" list details of a person responsible for an action that happended and because of that has been added to the log;

9. "Category" informs about a place in Jira, where modification occurred;

10. "Summary" columns lists basic information about logged action;

11. "Object" details which Jira element has been affected (i.e. workweek schemes, holiday schemes Jira groups, users, vacation manager teams, permission type, notification scheme, custom field etc.);

12. Upon clicking on a row it will extend its size and additional information can be seen if it exists i.e. IP address of an individual responsible for particular event.

  • No labels
$customFooter