Idea Exchange Promotion

Commit dates and where they're displayed within a task and their effect on Home has started to cause some confusion with our teams. It's hard to distinguish between a commit date and a planned completion date. Adjusting a projects timeline throws a wrench into things as well. Here's an existing Idea Exchange Ticket to change the UI and display the Planned Completion adjacent to the Commit Date: "https://support.workfront.com/hc/en-us/community/posts/360007989794-Task-Page-UI-update-Put-DUE-DATE-next-to-Commit-Date?flash_digest=a2d60dc4b1acad677a19548cfbdb37ecc158e938">https://support.workfront.com/hc/en-us/community/posts/360007989794-Task-Page-UI-update-Put-DUE-DATE-next-to-Commit-Date?flash_digest=a2d60dc4b1acad677a19548cfbdb37ecc158e938 Thanks All! Satchell Mische-Richter Quality Bicycle Products

I know I've said this before but it's becoming obvious that the Idea Exchange is just a way of making customers feel like their frustrations might be heard. Aileen Taylor Cell Signaling Technology

"https://support.workfront.com/hc/en-us/community/posts/115003152254-Create-Toggle-So-that-When-a-Proof-Comment-Is-Deleted-The-Corresponding-Comment-in-Update-Tab-Should-be-Erased-as-Well">When a Proof Comment is Deleted, the Corresponding Comment in Document's Updates Tab Should Also be Deleted In the Legacy proofing tool, the deleted comment remained in the proof with the user's name plus date/time of the comment with a line through it. You couldn't open the comment, but you could at least see when the comment was made and compare it to the comment in the document's updates tab to reasonably assume that was the deleted comment. In the new proofing tool, the deleted comment is completely gone from the proof. If you go into the Proof Details > Activity, you can see that a user deleted a comment plus the date/time to make the same reasonable assumption. But it seems a bit of a time-suck to have to go into yet another location to verify proof comments. For our proofing use... We have users who reply to proof comments within the document's Updates tab rather than within the proof (generally only when that user's stage has already been locked so they are unable to reply within the proof). Then we have some users on a private proof stage, so their comments do not transfer to the document's updates tab. This means our team has to go to both the proof and the document's Updates tab to verify they've captured all comments/edits. And now with the new proofing tool they have to go to yet another place to verify a deleted comment. Ideally, integration between the proof and the Updates tab would be complete and if a comment is deleted from a proof it would also be deleted from that document's Updates tab. But I'd settle for the comment remaining in the proof with the line through it as the Legacy Proofing had or some notation in the document's Updates that the comment has been deleted. Heather Slater Thermo Fisher Scientific Inc.

ABILITY TO TRACK TIME IN MINUTES At our organization, it's very common to work on multiple projects a day, for minutes at a time. It would help to have the option to track time in minutes to get an exact figure of how much time is being spent on each project or task. Please upvote if you agree! "https://support.workfront.com/hc/en-us/community/posts/360016118374-Ability-to-track-time-in-minutes">https://support.workfront.com/hc/en-us/community/posts/360016118374-Ability-to-track-time-in-minutes Hourie Alahaydoian Capital Group Intl

REMINDER NOTIFICATIONS SHOULD LINK BACK TO THE PROJECT OR TASK Currently when receiving reminder notification the email received is static and doesn't actually link to the project or task being referenced. This causes confusion because tasks can have the same name under different projects. (e.g., copyediting, etc.) I'd like to suggest a "See it in Workfront" link be added to each reminder email to make it easier and more efficient to link to the item from the reminder. Please upvote if you agree! "https://support.workfront.com/hc/en-us/community/posts/360016286113-Reminder-Notifications-should-link-back-to-the-project-or-task">https://support.workfront.com/hc/en-us/community/posts/360016286113-Reminder-Notifications-should-link-back-to-the-project-or-task Hourie Alahaydoian Capital Group Intl

Can I get an upvote! "https://support.workfront.com/hc/en-us/community/posts/115005868768-Ability-for-System-to-Automatically-Maintain-Status-on-Issue-if-Resolving-Task-Project-Completed-Prematurely?flash_digest=c41d7b1e5b1d7f9e867083ad8a52955a18ba9daf&page=1">ABILITY FOR SYSTEM TO AUTOMATICALLY MAINTAIN STATUS ON ISSUE IF RESOLVING TASK/PROJECT COMPLETED PREMATURELY Ok, I am curious if anyone else has noticed this, has issues with this, or has a better solution than what we are currently using to mange this. Back in 2012 when we started using Workfront I noticed for Issues that we convert to Tasks (we keep the Issue linked) if the user accidentally changed a Task Status to Complete and then changed it back to In-Progress or some other status, the Issue Status remained Closed. The Issue does not update to reflect the correction on the Task. When I had reached out to the Help Desk they indicated that this was "working as designed"; once the Issue Status is set to Closed it basically ignores any additional status changes on the Task. This creates problems for us because our Issues are using facing and we don't want to be signaling to the requester that something is complete, when it really isn't. So how do we try to manage this? We use an exception report. We have a report that shows the Issue Status and the Task Status and if they do not match, someone has to manually fix the Issue to "reset" the status. This involves going to the Issue, editing the overview tab to save the current value in the Task field, removing the This Resolves value, and saving the change. Then editing the Issue a second time to set This Resolves to Task and pasting the Task name back in the field, and saving it again. In my opinion....a lot of work when it would be more efficient is the system was able to handle it and I wish I knew why it didn't (....it's the little things....). I opened an Idea on the Exchange over a year ago (03/14/17) and it hasn't received much support. Another mystery... As of today the vote count is up to 6. Am I missing something here? Is there a better way to handle this in a more automated fashion, without having to resort to an API? The integrity of information that we have available to our end users is especially important, so I'd like to make this as seamless as possible without all the manual work. If you have a better mouse-trap please share! :) Admin Kelly-Wehrmann SSFCU

Upvote promotion: "https://support.workfront.com/hc/en-us/community/posts/360018678193-Buggy-Data-Editing-From-Reports-Attaching-Random-Form">Buggy Data Editing From Reports - Attaching Random Form Love the Workfront product, but this has been messing us up continually ever since they launched the ability to attach multiple forms a few years ago. If you edit custom data from a report, you have to be very careful that every item in the report has the correct form with the data field before starting the edits. If you do not, the system will go find any form out there with the data field and attach it to the item. We find random forms attached to things almost every week. Also, if the form contains other fields with default values, it actually acts to attach those attributes as well... all without any form of warning or notification of this happening in the background. Would LOVE upvotes on this one. Matt Marks Banner Engineering Corp.

For all Proofing users... Please upvote "Tag all the users" by Skye Boardman In the proof, I want to be able to tag any user in my Workfront environment. Not just people who have opened the proof. Not just people who are an owner or reviewer of the proof. Not just people who are in the advanced workflow. If any person has a user account in my Workfront instance, I would like to be able to tag them in any proof. Bonus points if you can code it to allow me to tag teams. https://support.workfront.com/hc/en-us/community/posts/115006961213-Tag-all-the-users Thanks! Amy Trahan Capital Group Los Angeles

Attn: Admins with users with multiple roles Please upvote: NAME POPULATION BASED ON JOB ROLE ASSIGNED By: Margaret Nelson Hi. I have users with two active roles: one primary at 75% and one other at 25%. I'd like to be able to see the users listed in the role on the Assignments drop-down on the Project for both roles. Right now, only the primary role is showing as, "Here are a few recommendations..." A solution would be to show users with a secondary role, though lower on the list, based on the second role's % for that role. "https://support.workfront.com/hc/en-us/community/posts/360017380134-Name-population-based-on-Job-Role-assigned">https://support.workfront.com/hc/en-us/community/posts/360017380134-Name-population-based-on-Job-Role-assigned Thanks, Amy Amy Trahan Capital Group Los Angeles

@Craig Smith and I would like your votes to lock down the project prioritization in the Resource Planner. "https://support.workfront.com/hc/en-us/community/posts/360018912053-Resource-Planner-Ability-to-lock-the-Project-Prioritization?page=1#community_comment_360002496794" Link to Idea Having spent months revamping the Alignment Score process so that the projects appear in the correct order in the Resource Planner, the simple act of clicking the orange 'Save' button has completely eradicated the order and there is no default view to which you can revert. Not good when you have 400+ projects! The documentation is going to be updated to alert people to this but we still need votes to change the functionality. "https://support.workfront.com/hc/en-us/community/posts/360018912053-Resource-Planner-Ability-to-lock-the-Project-Prioritization?page=1#community_comment_360002496794" Jane Bradshaw BAKKAVOR LTD