Results & Actions Configuration

After clicking Generate Activity Log results will be displayed in the results table. There are three views available: Aggregated View, Detailed View and Work item View. You can configure logged actions list by clicking “Actions” drop down menu.

List of the logged actions

image-20260724-093846.png

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

  1. Work item created

  2. Work item updated

  3. Work item deleted

  4. Work item 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. Work item link created

  10. Work item link 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. Includes user last login action (i.e. when the logged out user logged in, not when the logged in user opens Jira).
    3. 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.
    4. 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. Group 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. Group removed

    1. This actions triggered when the group is removed from the project.
    2. Retrieving this action into the app may take up to 30 minutes.

  34. User removed from project

    1. This action is triggered when a user or group is removed from the project via “People and access” (People and Role).
    2. Requires initial configuration of the connection to Jira Administration Log.
    3. Retrieving this action into the app may take up to 30 minutes.

  35. Group deleted

    1. Requires initial configuration of the connection to Atlassian Guard.
    2. Retrieving this action into the app may take up to 30 minutes.

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

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

  38. Version released

  39. Version unreleased

  40. Version created

  41. Version moved

  42. Version updated

  43. Version deleted

  44. Option voting changed

  45. Option watching changed

  46. Option unassigned work items changed

  47. Option subtasks changed

  48. Option work item links changed

  49. Option time tracking changed

  50. Sprint created

  51. Sprint deleted

  52. Sprint updated

  53. Sprint started

  54. Sprint completed

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

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

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

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

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

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

  61. Attachment created

  62. Attachment deleted

  63. Work item type created

  64. Work item type updated

  65. Work item type deleted

  66. Filter created

  67. Filter updated

  68. Filter deleted

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  90. Assets roles updated

    1. The action is logged every 30 minutes **
    2. Log visibility depends on the Assets and app permissions ***

  91. Assets object type roles updated

    1. The action is logged every 30 minutes **
    2. Log visibility depends on the Assets and app permissions ***

  92. User enabled site access

    1. Requires initial configuration of the connection to Atlassian Guard.
    2. Retrieving this action into the app may take up to 30 minutes.

  93. User disabled site access

    1. Requires initial configuration of the connection to Atlassian Guard.
    2. Retrieving this action into the app may take up to 30 minutes.

  94. User enabled organization access (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.
    1. User disabled organization access (requires Atlassian Guard on the instance)

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

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

  97. Work Item View

  98. User granted role (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.

  99. User revoked role (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.

  100. User removed from organization

    1. Requires initial configuration of the connection to Atlassian Guard.
    2. Retrieving this action into the app may take up to 30 minutes.

  101. User invited to organization (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.
  • These actions are retrieved every 30 minutes. Therefore the action can appear in the log maximum after 30 minutes.

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

*** 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 in the app AND the user has Jira Administrator permission.

The actions are visible for users with Administrator or Manager in the app or with Administrator role in Jira, unless the work item security is applied to certain work items. For the work items with the security level, only the number of actions will be visible in the Aggregated view.

previous Filter Configuration next Aggregated View