Table of contents

...

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:

...

You can share the saved filter with other users, user groups, projects, organizations or limit access by choosing the Private option:

...

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.

5. Status changed

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

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.

18. Project role updated *

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

19. Project role deleted *

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

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.

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

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

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

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.

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

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

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

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

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

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

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 changedOption attachments 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)

    1. Requires initial configuration of the connection to Assets.

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

    1. Requires initial configuration of the connection to Assets.

53. Attachment created

54. Attachment deleted

55. Issue type created

56. Issue type updated

57. Issue type deleted

58. Filter created

59. Filter updated

60. Filter deleted

61. Permission scheme created *

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

62. Permission scheme copied *

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

63. Permission scheme deleted *

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

64. Permission scheme updated *

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

65. Permission added *

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

66. Permission deleted *

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

67. Global permission added *

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

68. Global permission deleted *

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

69. Customer permissions changed *

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

70. Agent Portal Announcement Update Permission *

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

71. Permission scheme added to project *

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

72. Project roles changed *

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

73. JIRA Service Desk configuration *

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

74. Login-free portal settings changed *

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

75. Public signup enabled *

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

76. Public signup disabled *

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

77. Requirement for email verification for signup changed *

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

78. Help center permissions changed *

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

79. Help center updated *

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

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

...

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.

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:

...

After clicking the field, you will see:

• User who viewed the issue

• From where the issue was viewed

  • Issue View (Issue details)

  • Customer Portal

• When the issue was viewed

...

Restore deleted issue

You can easily restore a deleted issue from the Detail view! To do so, click “Restore deleted issue“ button and click “Restore“ in the confirmation popup:

...

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:

...