People tab of a project to dynamically update | Community
Skip to main content
NicholeVargas
Adobe Employee
NicholeVargasAdobe Employee
Adobe Employee
September 16, 2020
Declined

People tab of a project to dynamically update

  • September 16, 2020
  • 21 replies
  • 5068 views

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. 

    21 replies

    Show previous replies
    Anna_Asatryan
    Adobe Employee
    Anna_AsatryanAdobe Employee
    Adobe Employee
    June 11, 2024
    No text available
    B
    Bol-1
    June 24, 2024

    Completely agree with the above. This is extremely inconvenient and not a good way to use the tool. In addition to the email notification, this also forces projects that people are no longer on to show up in their projects lists. Having to manually remove from the "people" tab is NOT a good or logical workaround. HIGHLY inconvenient and confusing!

    K
    Kasey-Gagne
    Level 5
    September 5, 2024

    Curious if there is any update on this one? 

    NicholeVargas
    Adobe Employee
    NicholeVargasAdobe EmployeeAuthor
    Adobe Employee
    October 21, 2024

    According to the Product Manager, @anna_asatryan , this feature has not been added to the short-term roadmap for Workfront due to other priorities. 

    Anna_Asatryan
    Adobe Employee
    Anna_AsatryanAdobe Employee
    Adobe Employee
    November 8, 2024

    Hi All, 

     

    I appreciate the explanation on the need for this functionality. 

     

    While I fully understand how this could benefit the workflow, we currently don't have this behavior change prioritized near term. However this might be something we will revisit some time next year.

    A
    AnnaHolder
    Level 4
    December 2, 2024

    It also would be beneficial if the task/issue the person is assigned to is Complete/Resolved status, then remove them from People. That way there is still record of the person having done the work on their related work item, but the People section isn't cluttered with resources no longer working on the project. 

    K
    KristaTe
    Level 2
    February 25, 2025

    I don't really understand the difference between People and Share. Why are both needed? People really needs to be dynamically updated or maybe even disappear. So many unwanted emails...

    MoniqueEvans
    Community Advisor
    MoniqueEvansCommunity Advisor
    Community Advisor
    February 25, 2025

    @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.

    J
    jpavlovski
    March 27, 2025

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

    Anna_Asatryan
    Adobe Employee
    Anna_AsatryanAdobe Employee
    Adobe Employee
    April 8, 2025

    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!

    Show more replies
    Terms & ConditionsAccessibility statement

    Loading footer...