@JenlynMik - intake forms for what? What kind of requests are we talking - marketing items, full enterprise projects, product enhancements?

For us we like the use of task/issue approvals because it provides an audit trail that satisfies our audit team and keeps us out of trouble. However, as Skye mentions, I have experienced all of those with users when I've managed other instances. 

I'm gonna run some reports to see if the tasks still show as pending predecessors, etc to double check. Thank you.

That is good to know and something I will definitely test and look into. Thank you.

I was on a call recently where someone from Workfront mentioned it wasn't good practice to use Parent tasks as Predecessors.  We do this pretty regularly since often times the tasks nested under a parent all need to be completed in order for the next tasks to start. So, instead of listing every sing...

Switch to text mode and change your valuefield to this:   valueexpression=ROUND(DIV({actualDurationMinutes}/480),0)  

@ibmfur -  Since the value expression data isn't stored data for Workfront to reference to format your field is really what it comes down to. Another option to consider is using a calculated field on your objects vs a calculated column. Then workfront will store that data and can use it for formatti...

I was trying to remember the syntax of the field without looking and just had it wrong. Once I checked my reports today I saw it was "completed" and not "required"

Try this:     listdelimiter=<div> listmethod=nested(assignments).lists name=actual Wrk Assignment(s) stretch=0 textmode=true type=iterate valueexpression=CONCAT({assignedTo}.{name}," (",{role}.{name},") -",{actualWorkCompleted}/60,IF({actualWorkCompleted}/60>ABS(1)," Hours"," Hour")) valueformat=HTM...

@Ross_Barton  Are you running this on a task report?