correct term is hurtbox, but yea, I agree.Workfront should nerf the parent task arrow so it's easier to hit

This feature seems like a must with a tool as flexible and customizable as Workfront.We NEED to be able to discourage (restrict) bad practices through the design of the system.Seconding another user's note: For simplifying the training and again, restricting users from bad practices, we should be ab...

Can you elaborate on what the two extra clicks are?Is this for a custom form on a task or a project?There might be a workaround, but also, I think there are some improvements that can be made to the accessibility of custom form information

We are excited about this feature being added, but finding issue converting all out custom fields to use custom name fields due to a limitation with reports.The two issues are:1) Using the API name as the default "display name" in a column. This requires us to add a custom display name for every use...

For context we have a custom field that has a label of "Content Class" but an internal name of "contentClass"Anytime we add that field to a report we will have to manually add a custom display name to get it to display in a user-friendly manner.Additionally, this makes searching for these custom fie...

With the new API-friendly option for custom fields, I have found an issue with the default display of custom fields in reports.Columns headers should be user-friendly by default, not system friendly. Thus, they should use the label by default as that is what the average user is aware of.