-
Suggestion
-
Resolution: Unresolved
-
11
-
117
-
Summary
Site-admins should be able to delete addon users which are not longer in use
Steps to Reproduce
- Install any add-on. A new system user will be added with the name addon_atlassian*
- Un-installing the addon will not remove the addon user created in the step 1.
- Due to one of the Restricted functions in Jira Cloud applications, site-admins are not allowed to delete any system users
Expected Results
Addon user should be deleted automatically or hidden completely so that they will not show-up in the drop down list when try to at mention a user.
Actual Results
- Addon users are not deleted automatically when the addon is un-installed.
- Addon users are showing up in the drop down list whenever at mention any user.
Notes
If your Issues were mistakenly assigned to these add-on accounts, running this query should find them:
- assignee in membersOf("atlassian-addons-admin") OR reporter in membersOf("atlassian-addons-admin")
- is related to
-
ID-7185 Add on user for deleted add on still remain active in the user management
-
- Closed
-
[JRACLOUD-69084] Site-admins should be able to delete addon users which are no longer in use
Unable to remove BigPicture user after uninstallation and it persists at the very top of the "Teams" drop down, implying it is still active and causing confusion. Please bring this capability to remove!
Hi, is there any update on this request? This is causing confusion among our users. (Looks like external app still has permission to interact with space even though the external app has been uninstalled by site-admin).
This is really frustrating, since I keep getting questions from our distributed team about products that we no longer use but had at one point, integrated with Jira.
For e.g., testing team asks if they can get access to qtest, a product we evaluated but never bought a license - because the moment a user starts typing @test, they see qtest as the first option.
This is a debacle as Service Desk reports all show the add-on system users. Why is this so hard to fix?
This was fairly easy to do on-premises with some SQL searches and careful pruning. Even if there isn't a self-serve option, there's no reason why the Support team can't do this when requested.