Issue Summary

When viewing users in Atlassian Administration, the tooltip for the Last activity column states that Last Activity data can be delayed up to 24 hours.

The Log in as user button does not become active until the Last activity column is populated for that user.

This results in a delay of up to 24 hours before an admin can log in as a user. This can cause a delay for admins who are testing and validating their cloud migration.

Steps to Reproduce

1. Create a user in your cloud site.
2. Log in normally using this user account and generate activity (for example, create a Jira issue).
3. As an admin, find that user's account and confirm that Last Activity still shows Not seen on this site.
4. Click into that user's account.
5. Confirm that Log in as user is not clickable, and hovering over it displays You cannot log in as a user that has never accessed this site.
6. Wait up to 24 hours and repeat these steps. Once Last Activity is populated, you can then use the Log in as user button.

Expected Results

The Log in as user button becomes clickable as soon as the user generates activity.

Actual Results

The Log in as user button does not become clickable until up to 24 hours after the user generates activity.

Workaround

Currently, the only workaround is to wait up to 24 hours before logging in as the user.