Yes, I agree with the above. Also, you cannot send escalation email reminders on issues. This prevents an effective mechanism to enforce SLAs on request queues. please vote for this feature on the idea exchange: https://one.workfront.com/s/idea/0870z000000XhchAAC/detail.

As a marketing team, our users are regularly adding metadata to projects used for events and campaigns. Requirements for fields in the project metadata evolve, and so if we add a field to a project and have to update information to existing projects it requires manually bulk updating hundreds of fie...

I am very surprised this functionality is not available to ensure requestees respond to requesters within their SLA. Without this functionality admins are limited to subscribed report of issues outside of SLA which do not scale (especially since they are still sent if a team meets SLAs).

This is critical functionality for admins to meet the increasing needs to store more data in WF across objects while reducing hours (days) our users or admin team take to manually update hundreds of projects across multiple fields. Salesforce has very similar functionality to append different objec...

One use case is a user is working on a task, and she uses an update to add key progress to task, but then needs to stop and resume work. Rather than creating a new and duplicative update editing the comments/update would enable this. Also another use case is that users make spelling mistakes and ...