The new Slack integration with being able to post updates to Workfront is excellent, and will really improve efficiency on our team.Two suggestions for how to improve it (already!): Enable ability to tag multiple users.Allow for responding to other updates, specifically when a user has been tagged i...

Yes please! Slack has become a huge part of our business, and as we continue to promote Workfront as the operational system of record and driving more communication outcomes to be stored in the tool, this would allow for more seamless workflows to do that for the users.

Right now, when someone submits an issue, they do not receive a notification when the issue is closed. The person working on the issue that closes the issue gets a notification, but the person who submitted it does not. This is un-intuitive, notifying the party that already knows the issue was close...

This would definitely be a big help, even if rolled out in pieces (starts with custom forms, then reports, etc.). Any little bit would be a good move in the right direction.

Currently, the notifications in the 'Communication' bucket are all-or-nothing for the daily digest - you cannot individually select one of them to be part of a daily digest. You can individually select notifications from the other buckets, though, and it would be great if you could do the same with ...

How about not making it required, either? Would be great if we could default the Request/Issue name to be one of the fields from our Custom Form. I know this is more advanced functionality, but it would be so much smoother for 95% of our use cases.

One thing we have been using in the meantime is the business case tab on the project. If the custom form you want to export is on the project-level, you can setup your business case to include the project's custom forms and then export the business case. It comes with much more data than is needed, ...

We struggle with the current Life After Death settings because we do not want people to be able to add new tasks, change dates, or change assignments, but we need them to be able to edit the custom forms that are on tasks. Currently, the only way to do this is to activate the setting which allows ta...

We would love to be able to Subscribe to all Projects of a certain Template, or within a certain Group, Company, Portfolio, Resource Pool, etc. This would be a big win.

We would find it beneficial to be able to lock-down custom forms so that they, and the fields within, can only be edited by certain groups or individuals. We have encountered a couple scenarios where we want a custom form on a project that we do not want the PM/Project Owner to be able to modify - i...