| Info |
|---|
Audit logging is a built-in Jira feature. Vacation Manager only adds some of its additional information to these logs. |
Currently in audit log entries are placed when:
- user vacation days are:
- assigned,
- updated,
- deleted,
- 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.
Currently we work to add more audit logging and it includes: configuration, vacation types and vacation days logging- ,
- vacation type is:
- created,
- updated,
- deleted,
- configuration is:
- created (initial setup),
- updated,
- deleted.
To access it, follow the below presented steps ( you need to be logged in as Jira administrator):
- Open Jira Administration menu;
- Access "System";
- Click on "Audit Log".
%20-%20how%20to%20access%20it.png?version=2&modificationDate=1549887694281&cacheVersion=1&api=v2)
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):
%20-%20general%20overview.png?version=1&modificationDate=1549890783597&cacheVersion=1&api=v2)
- 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);
- Find all logs within particular time frame (days in calendar);
- Find logs tied with particular user - an individual that you look for must be present in "Author" (8), or/and "Object" (11) columns;
- Find logs within particular project (can be useful if you have more than one VACMAN project present)
- "Export" button - upon clicking on it you are to be presented with a prompt, similar like a one presented below:
%20-%20export%20button%20confirmation%20prompt.png?version=1&modificationDate=1549892253744&cacheVersion=1&api=v2&height=150)
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.
(TBC →After clicking "export", log is presented to be saved locally as an archived (.zip) file.
6. More menu contains additional options:
%20-%20more%20menu%20content.png?version=1&modificationDate=1549892771324&cacheVersion=1&api=v2&width=169)
More information in regards to auditing in Jira applications can be found here https://
...
...
...
adminjiraserver/auditing-in-jira-applications-938847740.html
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 happened 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.