Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

kdalen1
kdalen1New Participant

Enable Bulk Edit of Programs, including moving bulk to different portfoliosNew

Integrating the capability to bulk move Workfront Programs to a Workfront Portfolio is crucial for streamlining project management processes and enhancing user efficiency. The current limitation of manual, one-at-a-time processing for this task creates a bottleneck in workflow management. To address this, developers should prioritize the inclusion of bulk editing functionality for Workfront Programs, aligning it with the existing capability for Workfront Projects. This enhancement not only ensures consistency in user experience but also maximizes the utility of the platform. Potential implementation strategies include:Unified Interface: Design a user-friendly interface that allows users to select multiple Workfront Programs and initiate bulk moves with a few clicks.Customizable Filters: Integrate customizable filters to facilitate the selection of specific programs based on criteria such as status, deadlines, or assigned teams.Batch Processing: Implement a batch processing mechanism to handle the simultaneous movement of multiple programs, optimizing efficiency for users dealing with large project portfolios.Error Handling: Include robust error handling mechanisms to notify users of any potential issues during the bulk move process, ensuring transparency and mitigating the risk of data inconsistencies.Audit Trail: Incorporate an audit trail feature that logs all bulk move activities, providing users with a comprehensive record for tracking changes and troubleshooting if necessary.Assistance provided by an AI

Emily_Austin
Emily_AustinNew Participant

Allow Cross-Project Predecessors on TemplatesNew

Description - I'd like the ability to be able to create cross-project predecessors in project templates. Currently you're only able to create internal predecessors in templates. Cross-project predecessors are very powerful but can be time consuming to set up each time a new project is created and can cause user error if a person either forgets to set up the predecessor or does it incorrectly.  Why is this feature important to you - Our users work cross-functionally very often and we'd like to be able to link tasks between the different teams without having to manually create the predecessors for every project.  How would you like the feature to work - Ideally, we'd be able to set a cross-project predecessor on a task on Project A Template to a task on Project B Template. When a project is created from that template, I'd like to be able to either create a new project for all linked templates OR select an existing project to link.  Example 1: Marketing creates a project using Template A that has cross-project predecessors for Template B (which belongs to the Sales team). On the 'Create Project' page, they have the ability to create both projects.  Example 2: Quality has already created a project from Template B but didn't sets up any cross-project predecessors since Marketing hadn't yet created a project from Template A. When Marketing goes in to create a project from Template A, they have the ability to select an existing project to link their predecessors to (Quality's Project B). 

AllieDuNew Participant

Allow group admins to have full access for 'User Admin (All Users)' without making CREATE AND DELETE mandatoryDeclined

We would like to see the ability for Group Admins to be User Admins WITHOUT being required to also give them access to DELETE users. Since Workfront allows users with logged hours to be deleted, we have already run into an issue where a user with time billed was deleted. And now we have no way to tell who those hours belong to, which has caused some probably with our revenue reporting. In order to avoid this in the future -- we removed the ability for our group admins to delete users. Unfortunately, when we took away the ability to delete users -- it then removed the User Admin access rights, as Create and Delete are both required to give that functionality. Now our group admins are unable to even add users, as they get an error stating they do not have access to the job role. They are also unable to edit the federation ID -- which we require as we have SSO enabled (as I assume most other enterprise level users do as well). We don't think you should be able to have access to DELETE users in order to successfully be able to add users and update federation id's. I suspect other large enterprise companies, especially those whose revenue recognition is tied to hours and users, will run into this issue where a user is accidentally deleted and then they have big headaches. If you have, please vote! If you have not already, please take this as a WARNING and a PLEA for help. :) ------------------------------------------------------------------------------------------------------ Below is the feedback we received from WF support about both of these: Job Role: The product manager over this area has let me know that to be able to assign a user a job role which you do not have yourself, you must either be a system administrator or a plan license user with the "User Admin (All Users)" access in your access level. Federation ID: The ability to delete users is not directly tied to the ability to edit the Federation ID. The ability to edit the Federation ID comes from the "User Admin (All Users)" checkbox in the Users section of the Access Level. Even if you have "User Admin (Group Users)", "Create", and "Delete" all checked, you cannot edit the Federation ID. The problem for you guys is that "Create" and "Delete" are mandatory with "User Admin (All Users)".