Issue Summary

There is an inconsistency in the activity dates shown under user management for JSM users (agents and customers).

Example:

• In user management, searching for a specific user displays:
  • Has access on site - Last seen on: [Date A]
  • Jira Service Management - Agent Never visited

• However, the user's last activity with tickets is on [Date B].

• Opening the user profile from a ticket shows:
  • Has access on site - Last seen on: [Date C]
  • Jira Service Management - Agent Last seen on: [Date C]

This inconsistency makes it difficult to accurately determine user activity and manage user access. There appears to be a bug in the code related to how JSM roles are handled in the product access array, resulting in LAT not being stored for them.

Impact

Exporting users from user management to check their activity and disable them based on false activity dates is unreliable due to this bug.

Steps to Reproduce

1. Go to user management for a JSM site.
2. Search for a user with both agent and customer roles.
3. Observe the activity dates change different scenarios such as:
   • When JSM customer access is turned off only, the Last Activity Timestamp (LAT) persists.
   • When JSM agent access is turned off only (customer access remains), it says Never Visited.
   • When JSM agent access is turned off first and then customer access, LAT appears again.
   • When JSM customer access is turned off first and then agent access, LAT is still present.

Expected Results

Activity dates should be consistent and accurately reflect the user's last activity, regardless of role changes.

Actual Results

Activity dates are inconsistent and sometimes display "Never Visited" or outdated information.