The user has left the organization, so we suspended their account. If we remove them from groups and teams, will this affect their tickets in the projects?
HiĀ @Abilash
Thank you for your post.
No, removing groups and user permission won't affect the tickets. The user will be keeped as a user account itself.
Hope it helps
Hi Abilash, Matteo's right on the tickets, and I checked it on a test site today by pulling a suspended user out of their group, where their tickets still showed them as assignee and a JQL search on them returned the same count before and after.
What does need some care when you strip groups is everything else that still points at that person by name or by group. If that person is in a group used for approvals through a group picker field, with everyone in it required to approve, and approvals are still waiting on them, removing them can leave requests stuck at "Submitting Approval". I'd use the fix Atlassian gives for that: add temporary members to that group to approve or decline, or add a transition out of the approval status. I'd also check automation. If they own or act for any rules, Settings > System > Automation flows > Transfer User moves those references to someone else, though connection owners aren't transferred. Filters and dashboards they own can be reassigned under Settings > System > Shared Items with Change Owner.
Suspended users aren't billed, and suspension keeps their group memberships (https://support.atlassian.com/user-management/docs/remove-or-suspend-a-user/ ), so if you remove the groups now a later restore won't give them back and you'd have to add them by hand.
Are their groups used as approvers anywhere?
Hi Abilash,
Removing a suspended user from groups and teams will not impact the historical data on their tickets. They will still appear as the reporter, assignee (if currently assigned), commenter, or issue creator where applicable.
One thing I'd recommend checking is whether the user is referenced in any project roles, automation rules, approval workflows, filters, dashboards, or subscriptions. While the tickets themselves remain unaffected, these configurations can sometimes depend on a specific user and may need to be reassigned after the employee leaves.
As a best practice, review any open issues assigned to the user and transfer ownership of important filters, dashboards, and automation rules before completing the cleanup.
It looks like you're new here. Sign in or register to get started.
