Table of contents

...

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:

• Organizations audit log

• Administration audit log

• Assets audit log

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.

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

...

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:

...

You can select the desired user by checking the checkboxes on the left of the name of the user. The selected users will move to the top of the list:

...

You can clear the selected users with “Clear selected items“.

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.

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

...

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:

...

You can select the desired user by checking the checkboxes on the left of the name of the user. The selected users will move to the top of the list:

...

You can clear the selected users with “Clear selected items“.

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:

...

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.

...

...

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.

...

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

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 instance)

    Requires

    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 detail changed 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. Version released

31. Version unreleased

32. Version created

33. Version moved

34. Version updated

35. Version deleted

36. Option voting changed

37. Option watching changed

38. Option unassigned issues changed

39. Option subtasks changed

40. Option issuelinks changed

41. Option timetracking changed

42. Sprint created

43. Sprint deleted

44. Sprint updated

45. Sprint started

46. Sprint completed

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

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

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

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

51. Assets object created (requires Jira Service Management Premium)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.

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

53. Group created

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

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

55. Group deleted

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

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

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

58. Version released

59. Version unreleased

60. Version created

61. Version moved

62. Version updated

63. Version deleted

64. Option voting changed

65. Option watching changed

66. Option unassigned issues changed

67. Option subtasks changed

68. Option issuelinks changed

69. Option timetracking changed

70. Sprint created

71. Sprint deleted

72. Sprint updated

73. Sprint started

74. Sprint completed

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

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

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

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

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

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

81. Attachment created

82. Attachment deleted

83. Issue type created

84. Issue type updated

85. Issue type deleted

86. Filter created

87. Filter updated

88. Filter deleted

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

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

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

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

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

94. Attachment created

95. Attachment deleted

96. Issue type created

97. Issue type updated

98. Issue type deleted

99. Filter created

100. Filter updated

101. Filter deleted

102. Permission scheme created 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.

103. Permission scheme copied 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.

104. Permission scheme 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.

105. Permission scheme updated 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.

106. Agent Portal Announcement Update 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.

107. Permission deleted 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.

108. Global permission added 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.

109. Global permission deleted 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.

110. Customer permissions 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.

111. Agent Portal Announcement Update Permission 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.

112. Permission scheme added to project 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.

113. Project roles 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.

114. JIRA Service Desk configuration 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.

115. Login-free portal settings changed 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.

116. Public signup enabled *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.

117. Public signup disabled *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.

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

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

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

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

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

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

...

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:

...

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

...

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

...

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

...

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:

...