People tab of a project to dynamically update

[#1]

Description - Right now, the People tab of a project is not dynamically updated to people actually in that project. Anytime someone is added to a task or issue in the project, they are added to the People tab (or are the PO or other reasons). But then they remain in the People tab even if they are removed from the project tasks. 

Why is this feature important to you - If users are opting into emails for 'updates about projects I'm on' then they are getting these unnecessarily. This is a big issue when it comes to projects that act as the projects receiving issues/requests - those projects will never go away as long as we have the request queue feeding it, but more people are randomly added to the project and after a while they aren't needed to be there but are still getting the notifications.

How would you like the feature to work - The People tab should be a reflection of the current state of the project, and should not include users who have been removed as assignees. 

Current Behaviour - Users are added to the People tab when assigned to a task or issue, but if a user is removed as an assignee, they remain on the People tab. 

[#2]

@KristaTe The People tab drives the "Projects I'm On" reporting. Just because a person has view, contribute, or manage access to a project does not mean they are involved with the project. For example, a Project Manager may be on the same team as another Project Manager and in a pinch could help edit the project but it isn't theirs so it shouldn't show on any of their lists. If you've ever added a column to a project report to list the Project Users, that collection is the People tab.

It can be seen as a bit niche depending on use case, but absolutely both are needed with larger organizations.

[#3]

Wholeheartedly agree with the poster. This is desperately needed. We have architected a complex fusion+manual effort workaround, but THIS should not be needed! 

[#4]

Hi All,

We sincerely appreciate the discussion and the insights shared around this idea. While we recognize its potential benefits, this isn’t something we’re able to prioritize in the near term. That said, we may still revisit this in the future.

Thank you for your thoughtful contributions!

[#5]

Hi All,

Since we are unable to prioritize this work item in the foreseeable future, I am going to mark this as Declined. However, we will make sure we consider this feedback when we have the bandwidth to work in the area.

Thank you again for all your feedback and use case descriptions.