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]

When a Project Owner is changed, the old owner remains on the project team and continues to receive notifications. When task assignees are removed and replaced with another assignee, the old assignee remains on the project team and continues to get notifications.

I would like to see a "Reset Project Users" button in the People tab of Projects which would bring up a dialog with all 'inactive' project users without an assignment on any task and allow the batch removal of these inactive Project Users.

Thanks for voting this up!

Cheers,

Steve

[#3]

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. If they're opting into getting '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.

[#4]

I went to submit this same idea. This is driving me crazy and is much needed! To go beyond a 'reset' button, I propose the People section dynamically populate based on who is assigned to a task or shared with the project. We have so many times where we pull in a template for a new project, and then delete some tasks that may be irrelevant, and whoever was on those tasks are still added to People and getting notified of all kinds of things they don't need. They don't to turn off these related notifications bc need them for projects they ARE on. WF, please help with this!

[#5]

Have the same issue.  Do you ever find a resolution?

[#6]

YES!

[#7]

I would also love a toggle setting to add subscribers and/or resource managers to this list as well. We have a couple instances where that may be beneficial

[#8]

Please do this one, it is quite inconvenient for users.

[#9]

This is a major problem in our instance. Many users unsubscribe from emails because of this issue which causes problems for ACTUAL projects they are on. 

[#10]

I agree with Monique, there are many instances where we want people on projects when they are not assigned any tasks, like a Creative Director, or a brand assigned Strategic Steward, etc. I even have a Fusion scenario that adds these peole based on a whos who in the client form.

[#11]

Hoping this idea can be added to a future roadmap. Spending unnecessary time removing the same deactivated person(s) on project templates is not efficient. Even if this could be handled through a report to batch remove users in the meantime, would be beneficial.