Versions Compared

Version Old Version 100 New Version 101
Changes made by

Gia Jgarkava

Gia Jgarkava

Saved on

Key

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

Table of contents

Table of Contents
minLevel1
maxLevel6
outlinefalse
stylenone
typelist
printabletrue

...

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

...

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:

...

  • 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.

...

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.

...

  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 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 removed 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. 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.

  33. 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.

  34. Version released

  35. Version unreleased

  36. Version created

  37. Version moved

  38. Version updated

  39. Version deleted

  40. Option voting changed

  41. Option watching changed

  42. Option unassigned issues changed

  43. Option subtasks changed

  44. Option issuelinks changed

  45. Option timetracking changed

  46. Sprint created

  47. Sprint deleted

  48. Sprint updated

  49. Sprint started

  50. Sprint completed

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

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

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

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

  55. 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 ***

  56. 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 ***

  57. Attachment created

  58. Attachment deleted

  59. Issue type created

  60. Issue type updated

  61. Issue type deleted

  62. Filter created

  63. Filter updated

  64. Filter deleted

  65. 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.

  66. 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.

  67. 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.

  68. 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.

  69. 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.

  70. 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.

  71. 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.

  72. 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.

  73. 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.

  74. Agent Portal Announcement Update Permission *

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

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

  75. 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.

  76. 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.

  77. 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.

  78. 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.

  79. 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.

  80. 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.

  81. 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.

  82. 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.

  83. 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.

  84. 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.

  85. 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.

  86. Assets roles updated

    1. The action is logged every 30 minutes **

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

  87. Assets object type roles updated

    1. The action is logged every 30 minutes **

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

  88. Space created (COMING SOON!) ****

  89. Space deleted (COMING SOON!) ****

  90. Space archived (COMING SOON!) ****

  91. Space unarchived (COMING SOON!) ****

  92. Space marked as deleted (COMING SOON!) ****

  93. Deleted space restored (COMING SOON!) ****

  94. Space import (COMING SOON!) ****

  95. Space export (COMING SOON!) ****

  96. Space key updated (COMING SOON!) ****

  97. Space logo uploaded (COMING SOON!) ****

  98. Space permission added (COMING SOON!) ****

  99. Global settings changed (COMING SOON!) ****

  100. Global permission added (COMING SOON!) ****

  101. Global permission removed (COMING SOON!) ****

  102. Content restriction added (COMING SOON!) ****

  103. Content restriction removed (COMING SOON!) ****

  104. Issue view

Info

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

...

  2. 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
**** To enable these actions, the User Activity Audit Log for Confluence should be installed on the same Cloud instance! (COMING SOON!)

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.

...

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:

...

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.

...

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.

...

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:

...