This update is very frustrating - especially with more and more tools embracing workflow automation. Thank you though for the follow up! Be Safe John

This functionally would seem to be a day one item, no? Especially since Workfront is an Enterprise focused tool and many companies run on a fiscal calendar.

Not something I would need to do often. BUT A HUGE WIN and actually with the ability to do it, I might make some changes with users who I have told no to in the past. I assume the data captured prior will remain in the table for reporting?

I'd "settle" on the ability to have - custom field aliasing on a form so that the field names can more direct and to the point. When you have an enterprise wide instance of 2k+ users from many departments some field names become very UGLY - ability to rename SUBJECT from the request queue page.......

I'll jump onto this party car.... YES - especially since I was 'trained' to believe that Teams in Workfront was the best way to assign work over an individual. Which is IMHO the best way on a templates - so that you only need to modify the works in a team, vs updating the templates.

Agree — the inability to update records cleanly in 2019 is extremely difficult to understand. With a large user base like we have this would make adoption easier.

I'm actually somewhat surprised this hasn't received more upvotes... Along with the ability to add a Subtask Template too ;-) Okay I'm going too far I suppose :-)

I'll admit that Workfront can offer more automation or machine learning as it relates to custom forms. Custom forms are one of the great features of the tool, and also one of the more brittle/weak points. I suspect what your are looking for could be handled with a Calculated expression - but ...

This would be a great feature! But - great power comes great responsibilities I could see this being a nightmare for large instances unless there was someway to "stop services" at the Admin level as to not over-write production data (unless that is part of the intent) Honestly working in p...

This would also allow a Kanban Board to be used across teams for visibility purposes