[bug]: If a member is removed from a project, he can't be removed from assigned tasks.

[Plorenzo]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

When I remove a member from a project and that member has assigned issues, it's not possible to remove him from them.

Steps to reproduce

Create a project, add a few members, create a few tasks, assign the tasks.
Add a few new members and remove the original ones.
Try to remove the old member from an assigned issue.

Environment

Production

Browser

Safari

Variant

Self-hosted

Version

v0.24.1

[bhavyasaraswat2208]

@Plorenzo Thanks for your response. This is actually an intended feature, we don't want to remove the member as an assignee. We will though provide the name of the member who has been removed from the project in the list of assignees, to remove them from the assigned tasks.

[Plorenzo]

that's is not the case. I'm not asking for all task to be set to unassigned when a member is removed. What I'm asking is for an issue assigned to member A to be able assigned to member B (and unassign member A)once member A is not part of the project anymore.

Currently can't be done, member A does not appear in the list of users when assigning an issue, so if there issue is already assigned, you can't de-selected.

[bhavyasaraswat2208]

@Plorenzo Makes sense. We're coming up with an efficient way to resolve this and add a seamless fix for it.

[ZaLiTHkA]

if I may make a suggestion: what about adding the ability to either clear the "assignee" field entirely, or adding a small "x" button inline with an assignee name to remove just one specific member?

I feel like the former could make for a cleaner UI, but could potentially cause issues for teams that often use multiple assignees. whereas the latter would be a little more fiddly, but ultimately far more flexible.

[bhavyasaraswat2208]

@ZaLiTHkA Thanks for the input, we're looking into it with our product team and will come up with a smooth and refined solution.