We would like the default selection for a field to be a custom form setting and not a custom field setting, just like required field logic works. For example, we have a "Region" field that we use across many different custom forms for reporting purposes. If that Region field is used on a form that i...

This is available now

This seems to be available now

For our request queue custom forms, we have a calculated field for "scoring" that pulls in the value of all the fields in the form. That score is then used for triaging and prioritizing the requests. However, Workfront will not allow you to use the same value for multiple options within the same fie...

https://one.workfront.com/s/idea/0870z000000PSEhAAO/detail - this on the roadmap

Actually this is still occurring! Would love for this to be fixed / go back to the way it was.

THIS HAS BEEN IMPLEMENTED

Per our stakeholders , it would be really helpful if they could see the parent task name of subtasks in the Workload Balancer. Especially for projects with a lot of tasks, and sections of the same few subtasks for multiple parent tasks (i.e. Review brief, Create asset, Upload Asset for 5 different p...

Per my stakeholders, it would be good to know what methods of validation will be allowed (specifically will it allow for pattern matching / Regex). If it's simply character limits / text / number / email address that may be a bit limiting.

I agree!!!!! Assignees forget that they have a new request to work on by the time it is approved, and then don't get notified about the approval so they don't know that work can start.