Recent activity log

Recent activity log

Advanced User Manager keeps a persistent record of every change it makes to your site. The record is shown in the Recent activity card on the Overview screen of the admin console, and it is the fastest way to confirm what a bulk run actually did after the progress dialog has closed.

The activity log requires Jira administrator permission, like every other part of the app. A non-admin sees an empty feed rather than an error.

Where to find it

  1. Open the admin console. It opens on Overview.

  2. Look at the Recent activity card in the right-hand column, below Quick actions.

The card shows the six most recent entries, newest first. Each entry is one line of text plus a timestamp shown as Today · 14:52, Yesterday · 09:24 or 3 days ago · 11:08.

Before you have run anything, the card reads: "No recent activity yet. Actions you run here - deactivations, property updates, imports and group changes - appear in this feed."

What gets recorded

Every mutating action the console performs writes an entry. The wording below is exactly what you will see, with N replaced by the number of items.

Action you ran

Entry written to the feed

Action you ran

Entry written to the feed

Set properties on Jira users

Updated properties on N users

Set properties on external users

Updated properties on N external users

Bulk group operation, add

Added N users to N groups

Bulk group operation, remove

Removed N users from N groups

Activate accounts

Activated N users

Deactivate accounts

Deactivated N users

Add users → Bulk-create via CSV

Invited N users via CSV

Add users → Import last-seen data

Imported last-seen data for N users

Import external users from CSV

Imported N external users

Add as customer

Added N Service Management customers

Delete external users

Deleted N external users

Create a user property

Created user property "name"

Rename a user property

Renamed a user property to "name"

Delete a user property

Deleted user property "name"

Entries are colour-coded by a small dot: blue for creations and imports, purple for property updates, amber for group changes, green for activations and customer additions, red for deactivations and deletions.

How long entries are kept

The log is stored in the app's own Forge storage on your site, not in the browser. That means:

  • It survives page refreshes, sign-outs and different browsers or machines.

  • It is site-wide and shared. Every Jira administrator sees the same feed, including actions run by other administrators.

  • It keeps the 50 most recent entries. Entry 51 pushes the oldest one out permanently.

The log is capped at 50 entries and there is no export. If you need a permanent record of a large migration, take a screenshot or copy the entries out before you run further batches - a long day of bulk work can push an earlier run off the end of the log.

Using it to confirm what a bulk run did

The progress dialog for a bulk action disappears once you dismiss it. The activity log is what remains, so use this sequence when a run finishes:

  1. Note the success and failure counts in the result dialog before closing it, along with any error message shown.

  2. Go to Overview and read the top entry in Recent activity. Its number is the count of items the app successfully changed.

  3. Compare that number with how many rows you selected. A gap means some rows failed - see the troubleshooting notes below.

  4. Verify the result on the data itself: for activate/deactivate, go to Jira users and switch the status control to Inactive or All (it defaults to Active, so deactivated accounts disappear from the default view); for property or last-seen changes, turn the relevant columns on from the Columns popover.

Reading a gap between selection and entry

  • Fewer users than you selected, on a deactivation. The accounts the app could not change were almost certainly not managed accounts of your organization. Check the amber pre-check panel that appears before a status change.

  • No entry at all. Nothing succeeded. The action failed for every selected row, so there was nothing to record.

  • Fewer users on a last-seen import. Rows whose account could not be matched, or where no property was written, are not counted.

  • Fewer external users on a delete. Records whose Service Management portal access could not be revoked are deliberately kept so you can retry them.

Limits you should know about

The feed records outcomes, not an audit trail. Do not treat it as a compliance record - it does not identify individual users, and it cannot be exported.

  • Only successes are recorded. A run in which everything failed writes no entry. Failures are reported in the result dialog at the time and nowhere else.

  • No per-user detail. An entry says how many accounts changed, never which ones, and never which property or group value was applied.

  • The administrator who ran the action is not shown. The app stores it with the entry, but the feed displays only the message and time.

  • Group operations report what you asked for. The entry counts the users and groups you selected, not how many individual add or remove calls succeeded. Check the result dialog's failure count for group runs.

  • A rename does not record the previous name. The entry shows only the new one.

  • No search, filter or full history view. Only the six newest entries are visible; older ones, up to the 50-entry cap, are held but not displayed.

  • Nothing here can be undone. The log is a record, not a rollback. Deactivation is reversible by activating the account again; deletions and property deletions are not reversed from this screen.

Actions taken outside the app - a change made directly in admin.atlassian.com, in Jira's own user management, or by an identity provider - are never recorded here. The log covers only what Advanced User Manager did.

Related

The Activity & last seen screen in the sidebar is a different feature: it reports when your users last used each Atlassian product. It is not a record of administrative actions.