Adobe Workfront

Description - When setting up a request queue with different queue topics, it would be really helpful to limit who can see each queue topic. Why is this feature important to you - This would allow users to only see topics that apply to them while minimizing the number of queue projects in the system. How would you like the feature to work - Allow for the "Queue Settings" to be applied differently across each queue topic. Each "Queue Topic" would have its own settings with a checkbox to inherit the projects settings or to customize the queue topic's settings. Also allow for sharing within each queue topic so we could provide proper visibility into each topic. Current Behaviour - For every topic that needs different visibility, a whole new request queue needs built which causes a lot of clutter in the initial request screen.

Often we as Fusion develpoers can't go deeper than checking API responses, even with the DevTool.I would be just another level if we could for at least the Workfront and Authenticator Modules be able to see deeper logs behind the API calls and their responses. Otherwise we always have to involve support.The the idea would be to provide on option to check deeper logs in Fusion Flow Executions if needed.Have a good day

Description - Ability to report on tasks only when all dependent predecessors have been marked as complete; otherwise, the report should not show that task as something that's ready to be worked upon.Why is this feature important to you - Our teams heavily depend on previous task completion to begin the next work. With that there is a lot of time that would be spent manually on going through all tasks to see what is ready.How would you like the feature to work - If I look at a task reportCurrent Behaviour - tasks shows even if one of the predecessor is marked as complete and the task actually has more than one predecessor. Only when all predecessors tagged on that task are complete, then show me the data. Copy of the report I created while working with Adobe ticket assistance and we didnt achieve what was needed.https://deloitte.my.workfront.com/report/6877aaea000166e652c792ceb63b6ae0/detail

On the new "Subscribing to Items in Workfront" feature that was just released this week, it would be awesome to bulk subscribe to a list of items. This came up from those looking to cover while another team member is out. Right now you can only do it from the going to each landing page and subscribing individually.

Description:Allow users to highlight areas in a proof when replying to comments, not just when creating new ones.Importance:Stakeholders often miss highlighting content or only mark part of what's relevant. This would improve clarity and streamline review workflows.How it could work:When replying to a comment in a proof, users should have the option to create a new highlight linked to their reply.Current Behaviour:Highlighting is only available when adding a new comment, not when replying to an existing one.

Description - When marketing operations use workfront planning for their campaign planning, the stakeholders would want to convert a plan (planning record) into a brief (request) in workfront. post this conversion either using fusion or manual request submission, the ideal experience for a 360 view of a campaign plan would be to link the brief (request) back to the campaign plan. However the current planning config doesn't have option to relate a request object record.Why is this feature important to you - This impacts the brief intake process and indicate a critical gap between Workfront planning and Workfront on a Content Supply Chain workflow for a Marketer.How would you like the feature to work - Create a relationship connection between Workfront planning record type with Workfront request object.Current Behavior - No Option to relate Workfront Planning record with Request object in Workfront

We would like to add the same person to a review route twice in different stages. We have the project owners review proofs in stage 2, but then also need to review again in the last stage after everyone else has reviewed, so they can review other's comments, comment back for clarification or answer any questions.Why is this feature important to you - Streamlines the process. Currently, the project manager has to reach out to the project owner after the route is complete to confirm there aren't any comments that need to be responded to, and wait for the project owner to reach back out to them when they've had the chance to review again. If they can be added again to the final stage, they will get the automatic email notification that it's their turn again. Once the review is complete, the PM knows it can be routed straight back to the necessary team without any additional steps in the process. 

It would be great to allow administrators to set specific and unique error pages when a login error happens. I have two types of users in my system. Those who authenticate with SSO and those who do not and use the mydomain.my.workfront.com/login page to log in directly and manage their password. Unfortunately, any user who errors out of SSO authentication bounces to that /login page which then causes an error loop for many users who do not realize that they can't log in through that page with their SSO credentials.It would be better if I could set a specific error page that directs them to help articles on how to resolve their SSO error and get to log in again rather than redirecting them to the /login page. But I need to keep that /login page as the error page for my users who do NOT use SSO. I need both options available because I have two separate use cases here.

In marketing, we work with many files that are animated GIFs for motion in social media and paid media channels. When our teams need to review these files, it's very difficult now with only allowing individual GIFs to be reviewed as a single proof. You should be allowed to upload multiple GIFs and create a single interactive proof where the GIFs are animated. As it stands today, you must upload every individual GIF to see animation and it can create up to 20+ proofs for someone to review which isn't reasonable. Our teams end up not using the proofing for all animation because no one is going to review 20+ links when they can just open up the files on their computer instead. This is the current rule in place: You can combine GIF files; however, please note that animated GIFs will be processed as static and NOT interactive. Future state: You can combine GIF files; and animated GIFs will be processed as fully interactive proofs.

Description - Deadline reminder notifications aren't being sent to the assigned to user after the task constraint is changed before the task is due during the lift of the project. I had submitted a case with Adobe Support and they concluded that changing the task constraint while the project is current blocks the user assigned to the task from receiving the deadline reminder that is set up in the automatic reminder section. It would be helpful to have the deadline reminder notifications to still be sent to assigned users of tasks even after the task constraint is changed during the life of the project. Why is this feature important to you - Users are losing track of tasks they need to complete after the task constraint on tasks their assigned to is changed. They no longer received the system deadline reminders which is causing them to miss completing those tasks on time. We strive to have tasks completed by their planned completion dates regardless of the task constraint set.&nbsp