Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of contents

...

Info

If you have IP allowlisting enabled on your Cloud instance (this is possible Jira for Premium plans), please contact us for the IP to be added to the cloud allowlist. Without this, some actions will not be logged.

Historical Actions in the Logs

For all the actions it is possible to see the log starting from the installation of the plugin. However, for the issue- and asset-related actions, also historical data, starting from January 1st, 2022 will be also available in the app. With the first install, you will see the corresponding informational message:

...

After the first install, depending on the number of issues and Asset objects, retrieving historical data may take from minutes to hours.

The actions on the following components are not available in the historical data and only the actions done after the app installation will be visible:

  • Global feature enable/disable

  • Board

  • Sprint

  • Version

  • Users

  • Project category

  • Comment update old value

  • Issue deleted

  • Actions from Jira administration audit log

  • Jira organization audit log

  • Assets audit log

  • Issue view

If you need to log additional actions, configure permissions, and add fields for monitoring, please visit Settings. From here you can configure connections to retrieve actions from:

Basic Search

Using the basic search, you can define several terms from your Jira instance for filtering the users for which you would like to see the results in the audit log. There are the following options:

  1. Calendar

  2. User

  3. Group

  4. People in Projects

  5. People in Organizations

  6. More

    1. Status changed

    2. Resolution set

    3. Fields

Calendar control is used for choosing a date or range of dates:

...

To choose a range, you can click a starting date followed by an ending date of the range. To choose a single day, simply click on a desired date, and if it is part of a selected range, click the same date again. In addition, predefined dates can be chosen from the left panel of the calendar.

Info

By default, the last 30 days are selected in the calendar.

After selecting the desired date or range, click Update to confirm the selection.

Info

You can only select the maximum 1-year range. In case of selecting a wider range, the corresponding message will show up and the Update button will be disabled.

...

Basic Search

Using the basic search, you can define several terms from your Jira instance for filtering the users for which you would like to see the results in the audit log. There are the following options:

  1. Calendar

  2. Project

  3. User

  4. Group

  5. People in Projects

  6. People in Organizations

  7. More

    1. Status changed

    2. Resolution set

    3. Fields

Calendar control is used for choosing a date or range of dates:

...

To choose a range, you can click a starting date followed by an ending date of the range. To choose a single day, simply click on a desired date, and if it is part of a selected range, click the same date again. In addition, predefined dates can be chosen from the left panel of the calendar.

Info

By default, the last 30 days are selected in the calendar.

After selecting the desired date or range, click Update to confirm the selection.

Info

You can only select the maximum 1-year range. In case of selecting a wider range, the corresponding message will show up and the Update button will be disabled.

...

With the Projects you can filter the action in the results that were done in certain projects. The existing projects will be displayed in the dropdown after typing the first letter:

...

User filter enables you to select a certain user or users on the instance, for which the action log should be displayed in the results. To choose the user, start typing the name, surname, or email of the user. The possible options will be displayed in the dropdown after the first letter:

...

Besides users, you can select users Group(s), People in Project(s) and/or Organizations(s). After selecting filters, click Generate Activity Log button to see the results based on the selected filters.

...

More filters

By clicking the “+More“ button, you can also filter the actions by Status changed, Resolution set and Fields:

...

You can also enhance search using JQL. If you already preliminary have already selected the filters in Basic Search, by toggling to JQL, the filters can be enhanced additionally with JQL. Pre-defined selections will remain and filter the results:

...

Info

With JQL you can filter only the actions related to the issues.

With the buttons on the right side of the field it is possible totext field, you can:

  • Expand the JQL field;

  • See the help page for JQL (will be opened on a new tab);

  • Display results based on the JQL term (identical to clicking Generate Activity Log button).

After typing in the JQL term, click Generate Activity Log button to see the results based on the selected filters.

Info

Due to the limitation of the corresponding Atlassian API, it is possible to retrieve at most 101,000 issues. If your search retrieves more issues, you will see the corresponding message and refine your search to view more actions.

...

...

Info

Adding a JQL filter limits the filter scope to only show actions performed in issues, and exclude other types of activities.

Manage Saved Filters

It is possible to save and manage filters for future use. After filling in the filters or JQL, click Save Filter text and fill in the “name” and “description” fields to save the filter:

...

If no subscription is configured, you will see the popup to add a new subscription:

...

When you click the “Add subscription“ button, you will see the popup where you can configure a subscription.

...

Info

All the subscription schedule times are displayed in UTC!

Results

After clicking Generate Activity Log results will be displayed in the results table. There are three views available: Aggregated View, Detailed View and Issue View.

List of the logged actions

Info

For the list of logged Confluence actions, see Confluence logs.

  1. Issue created

  2. Issue updated

  3. Issue deleted

  4. Issue resolved

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  5. Status changed

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  6. Comment added

  7. Comment updated

  8. Comment deleted

  9. Issuelink created

  10. Issuelink deleted

  11. Worklog created

  12. Worklog updated

  13. Worklog deleted

  14. Project created

  15. Project updated

  16. Project deleted

  17. Project role created *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  18. Project role updated *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  19. Project role deleted *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

    3. Retrieving this action into the app may take up to 30 minutes.

  20. Project category changed *

    1. Requires initial configuration of the connection to Jira Administration Log.

  21. User created

    1. This action also logs “Invite user“ and “Grant access“ actions from Atlassian Guard

      1. Requires initial configuration of the connection to Atlassian Guard.

    2. Retrieving this action into the app may take up to 30 minutes.

  22. User updated

  23. User deleted

    1. This action also logs “Remove user“ and “Revoke access“ actions from Atlassian Guard

      1. Requires initial configuration of the connection to Atlassian Guard.

    2. Retrieving this action into the app may take up to 30 minutes.

    3. Due to the API restrictions, in case of “user deleted“, the author of the action will be indicated as JIRA.

  24. User deactivated (requires Atlassian Guard on the instance)

    1. Requires initial configuration of the connection to Atlassian Guard.

    2. Retrieving this action into the app may take up to 30 minutes.

  25. User reactivated (requires Atlassian Guard on the instance)

    1. Requires initial configuration of the connection to Atlassian Guard.

    2. Retrieving this action into the app may take up to 30 minutes.

  26. User last active

    1. The Data/time when the last action of the user was logged either in the Administration, Organization or Assets log.

    2. Except for the rare cases after changing the logic of defining last action (10-Jul-2024), only one “last active“ log will be visible in the log.

    3. Retrieving this action into the app may take up to 30 minutes.

  27. User removed from site (requires Atlassian Guard on the instance)

    Requires

    added to group

    1. Viewing the actor requires the initial configuration of the connection to Atlassian Guard, otherwise the actor will be visible as JIRA.

    2. Retrieving this action into the app may take up to 30 minutes.

  28. User invited to site (requires Atlassian Guard on the instanceremoved from group

    1. Viewing the actor requires the initial configuration of the connection to Atlassian Guard, otherwise the actor will be visible as JIRA.

    2. Retrieving this action into the app may take up to 30 minutes.

  29. User removed from site (requires Atlassian Guard on the instance)

    1. Requires initial configuration of the connection to Atlassian Guard.

    2. Retrieving this action into the app may take up to 30 minutes.

  30. User invited to site (requires Atlassian Guard on the instance)

    1. Requires initial configuration of the connection to Atlassian Guard.

    2. Retrieving this action into the app may take up to 30 minutes.

  31. User detail changed (requires Atlassian Guard on the instance)

    1. Requires initial configuration of the connection to Atlassian Guard.

    2. Retrieving this action into the app may take up to 30 minutes.

  32. Version released

  33. Version unreleased

  34. Version created

  35. Version moved

  36. Version updated

  37. Version deleted

  38. Option voting changed

  39. Option watching changed

  40. Option unassigned issues changed

  41. Option Group created

    1. Retrieving this action into the app may take up to 30 minutes.

  42. Group removed

    1. Tis actions triggered when the group is removed from the project.

    2. Retrieving this action into the app may take up to 30 minutes.

  43. Group deleted

    1. Retrieving this action into the app may take up to 30 minutes.

  44. Api token created

    1. Requires initial configuration of the connection to Atlassian Guard.

    2. Retrieving this action into the app may take up to 30 minutes.

  45. Api token revoked

    1. Requires initial configuration of the connection to Atlassian Guard.

    2. Retrieving this action into the app may take up to 30 minutes.

  46. Version released

  47. Version unreleased

  48. Version created

  49. Version moved

  50. Version updated

  51. Version deleted

  52. Option voting changed

  53. Option watching changed

  54. Option unassigned issues changed

  55. Option subtasks changed

  56. Option issuelinks changed

  57. Option timetracking changed

  58. Sprint created

  59. Sprint deleted

  60. Sprint updated

  61. Sprint started

  62. Sprint completed

  63. Board created (will not be logged for Discovery Project boards)

  64. Board updated (will not be logged for Discovery Project boards)

  65. Board deleted (will not be logged for Discovery Project boards)

  66. Board configuration changed (will not be logged for Discovery Project boards)

  67. Assets object created (requires Jira Service Management Premium))

    1. Requires initial configuration of the connection to Assets.

    2. Retrieving this action into the app may take up to 60 minutes.

    3. Log visibility depends on the Assets and app permissions ***

  68. Assets object updated (requires Jira Service Management Premium)

    1. Requires initial configuration of the connection to Assets.

    2. Retrieving this action into the app may take up to 60 minutes.

    3. Log visibility depends on the Assets and app permissions ***

  69. Attachment created

  70. Attachment deleted

  71. Issue type created

  72. Issue type updated

  73. Issue type deleted

  74. Filter created

  75. Filter updated

  76. Filter deleted

  77. Permission scheme created *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  78. Permission scheme copied *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  79. Permission scheme deleted *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  80. Permission scheme updated *

    1. Requires initial configuration of the connection to AssetsJira Administration Log.

    2. Retrieving this action into the app may take up to 6 hours 30 minutes.

  81. Assets object updated (requires Jira Service Management Premium)Permission added *

    1. Requires initial configuration of the connection to AssetsJira Administration Log.

    2. Retrieving this action into the app may take up to 6 hours 30 minutes.

  82. Attachment created

  83. Attachment Permission deleted

  84. Issue type created

  85. Issue type updated

  86. Issue type deleted

  87. Filter created

  88. Filter updated

  89. Filter deleted

  90. Permission scheme created *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  91. Global permission added *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  92. Permission scheme copied Global permission deleted *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  93. Permission scheme deleted Customer permissions changed *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  94. Agent Portal Announcement Update Permission scheme updated *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  95. Permission scheme added to project *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  96. Permission deleted Project roles changed *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  97. Global permission added JIRA Service Desk configuration *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  98. Global permission deleted Login-free portal settings changed *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  99. Customer permissions changed Public signup enabled *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  100. Agent Portal Announcement Update Permission Public signup disabled *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  101. Permission scheme added to project Requirement for email verification for signup changed *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  102. Project roles Help center permissions changed *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  103. JIRA Service Desk configuration Help center updated *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  104. Login-free portal settings changed *Scheduled deletion of account

    1. Requires initial configuration of the connection to Jira Administration LogAtlassian Guard.

    2. Retrieving this action into the app may take up to 30 minutes.

  105. Public signup enabled *Canceled deletion of account

    1. Requires initial configuration of the connection to Jira Administration LogAtlassian Guard.

    2. Retrieving this action into the app may take up to 30 minutes.

  106. Public signup disabled *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  107. Requirement for email verification for signup changed *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  108. Help center permissions changed *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  109. Help center updated *

    1. Requires initial configuration of the connection to Jira Administration Log.

    2. Retrieving this action into the app may take up to 30 minutes.

  110. Scheduled deletion of account

    1. Requires initial configuration of the connection to Atlassian Guard.

    2. Retrieving this action into the app may take up to 30 minutes.

  111. Canceled deletion of account

    1. Requires initial configuration of the connection to Atlassian Guard.

    2. Retrieving this action into the app may take up to 30 minutes.

  112. Issue view

...

  1. Assets roles updated

    1. The action is logged every 30 minutes **

    2. Log visibility depends on the Assets and app permissions ***

  2. Assets object type roles updated

    1. The action is logged every 30 minutes **

    2. Log visibility depends on the Assets and app permissions ***

  3. Issue view

Info

* These actions are retrieved every 30 minutes. Therefore the action can appear in the log maximum after 30 minutes.

Info

** The action is logged every 30 minutes. This means that the log will reflect the changes at the moment of the synchronization. If the schema role is updated several times during this 30-minute period, the log will reflect only the first and the last updates.

Info

*** These actions will be visible if:

  • The user has Administrator or Manager role in the app AND the user is added to one of the roles of the corresponding Assets schema:

    • Object schema managers

    • Object schema developers

    • Object schema users

  • The user has Administrator or Manager role in the app AND the user has Jira Administrator permission.

Info

The actions are visible for users with Administrator or Manager roles in the app or with Administrator role in Jira, unless the issue security is applied to certain issues. For the issues with the security level, only the numberof actions will be visible in the Aggregated view.

Aggregated View

The Aggregated view shows all the actions based on action authors in the rows:

...

You can check or uncheck “Select all“ checkbox to select all or none of the columns. Clicking “Reset default”, will select the default columns (Issue Created, Issue Updated, Issue Deleted, Issue Changed, Status Resolve, Issue Commented, Comment Updated and Comment Deleted).

...

Additionally, you can filter the data based on transitioned statuses. Click +More button across the use filters and select Status changed and/or Resolution set:

...

After selecting the option(s) you will see the additional filters below the user filters:

...

Click Status Change button and choose “from“ and “to“ from the available statuses list (you can select more than one status):

...

When you select the desired statuses, click Apply button and Generate activity log to filter the actions:

...

In the same way, you can filter the actions by the Resolutions:

...

Info

Keep in mind, that unlike user filters, status change and resolution filters work with AND confidion i.e. If you filter statuses

...

Results Breakdown

Additionally, you can break down the results in the aggregated view by:

  • Project

  • Destination status

  • Transition

  • Issues [coming soon!]

  • Fields [coming soon!]

Breakdown by Projects

You can break the actions down by projects. To do so, click Breakdown button and select Projects:

...

You can break the actions down by the destination status to see how many times the user transitioned the issue into the statuses. To do so, click Breakdown button and select Status.

...

You can break the actions down by the transitions to see how many times the user transitioned the issue from one status to another. To do so, click Breakdown button and select Transition.

...

You can break the action by the issues. To do so, Breakdown button and select Issues.

...

You can break the action by the fields that were updated. To do so, Breakdown button and select Fields.

...

Info

The actions in the issues with a security level, will not be visible in the detail view for the users who have no access to the issue!

For each action you can see the following information:

...

  • User who did the action

  • Which action was done

  • When the action was done

  • The affected object

    • In case of issues:

      • Issue key

      • Issue type

      • Issue summary

      • Request type

      • You can see the issue key and can open the issue by clicking Open button.

  • Changes

    • Old value and new value

      • Some of the actions (e.g. “Version released”, “Version unreleased” and , “Asset Created” actions does ) do not have Changes section.

...

Info

If a single issue is viewed several times during 5 minutes, this is considered as a single issue view. The Issue View actions for the issues with the Security Level, will not be visible in the list, unless the security level was applied before January 1st, 2022 and no actions were done in the issue before July 30th, 2024.

...

You can see the following information in the list:

...

You can also export the Issue views in Excel format by clicking “Export (.xlsx)“ button.

Info

You will see the Issue View actions, only if your Jira user has Browse Projects permission for certain Projects/Issues. The view actions will also be visible for the issues with issue security for the users who have permission to view the issue.

Who viewed the issue

After installing the app on the instance, you can also see who and when viewed the issue, from the issue details. To do so, click, “Open User Activity Audit Log” field from the issue details:

...

Date

Author

Target

Action

Project

Old

New

ID/Issue Key *

Issue Type

Info

* Depending on the action may contain an Issue Key, project ID, version ID, user ID, Sprint ID, etc.

Export history

From the app Header → Export history, you can view all the exports made by the users:

...

In case of the Saved filters, you will be able to click the Filter name (in blue) and the saved filter will open. For the unsaved filter, “custom“ will be shown in the Filter name.

...

If you are configuring the webhooks for the first time, you will see a popup with “+ Add URL endpoint“ button:

...

When you click “+ Add URL endpoint“ button, you will see a window where you can generate you access token for the API:

...

Name the endpoint and click “Generate access token” button to generate a token:

...

Click Add Token button to save the token:

...