Why Jira Add-Ons Show as Disabled/Enabled by Anonymous User (Cloud)

Summary

Checking the Managed Apps audit log, you see that some Add-on apps have been installed, disabled, or even enabled by an anonymous User.

Environment

Cloud

Cause

Currently, this is known behaviour in Jira.

Typically, the anonymous entries relate to system update events when there are updates for pre-existing apps.

You might see anonymous user in the Marketplace app logs because:

• This occurs when the system installs an app from the backend because a purchase order for the app was submitted. The user information is not shown correctly on the UI and appears as anonymous.

• When Jira automatically updates an app, it shows an 'anonymous' message instead of a detailed one.

• Sometimes, apps will be installed by an anonymous user if the app is a Connected App.

Non-admin users can't install apps via the Marketplace, but they can allow access to some apps through the external apps UI. When you click on a Jira link from within that app, you are prompted to grant the app access to your Jira site. These apps are Connected Apps, which you can view and manage via the link.

We have an open feature request to handle this situation better, and you can view, vote, and comment on it:

• JRACLOUD-67314: Show user responsible for action on Add-on Audit Log

FAQ:

Could you please let us know the reason why it was disabled?

When an update occurs, it shows as anonymous because it is coming from a third party. Generally, during an update, the app should continue to work, but there might be a momentary blocker.

If you want to ensure there was a release on the X date, please contact the third-party app supplier. Check their support page for more details.

If an app upgrade occurs, is there a way for admins to be notified, for example by email?

There is no standard way to do this.

You can watch for upgrades to an app on the Marketplace. It will notify you whenever a new version is available.

For example, for Xray, go to Xray Test Management for Jira Overview on the Atlassian Marketplace. Select Watch App from the More Options (⋯) Menu. But the "when" and "if it gets upgraded" on your instance will vary.

Can site admins control the upgrade timing?

Unfortunately, it is not possible.

The system checks for updates every 24 hours, around midnight. Some randomization is added to the time to ensure that not all instances overload our servers with update checks simultaneously.

Is there a period when the app does not function during an app upgrade (assuming the upgrade works)? From the logs, we see X seconds between the start and end of the upgrade.

App updates generally don't stop functionality. However, the third-party app vendor can better clarify the dynamics of the type of release and whether it impacts the functionality during the update's time lapse.