One of the apps (add-ons) in Jira was disabled when anonymizing a user. As a result, some of the user data hasn’t been anonymized and the app itself is inconsistent.
If a 3rd party app has been optimized to work with the user anonymization, it’s notified about a user being anonymized through extension points that connect it to Jira. Once notified, the app can take appropriate actions and anonymize any related user data that it stores. If the app is disabled, it simply doesn’t know a user is being anonymized, leaving original data intact.
To solve this problem, enable the app and retry the anonymization. This time, we’ll anonymize only outstanding data—in this case, it will be the data stored in the app. For more info, see Retrying anonymization.