Done! I do love a Maze 

Yeah, it wasn't a great experience for us to have our proof creators have to make a decision. We have our templates set to have the proof creator/owner only in the first stage, and set as a Reviewer, not a Reviewer & Approver. Then, the second stage starts upon proof creation for the person/people r...

We used to have multiple, and very detailed, custom forms, but we learned our users were much more apt to use Workfront when we simplified our intake process. Now, we only have one form with these questions (with a few dropdown lists and logic added where it makes sense). Our Marketing Specialists c...

My main issue is I can't seem to stop people from using the Description field as a very long memo @JillAc we used to have that problem too, until we discovered we could uncheck the description field from the request queue details (New Request Fields). We added in our own custom description fields in...

That's great! And appreciate the solution added, it's always helpful 

I should have known, it's never that easy! I'm sure there's a way you can get there. If the task name is always the same, you could add the "Task Name >> contains (then add your task name)" to the Filter Rules, for example. But that's is a very specific filter - you'd have to be careful with naming ...

Did you try adding Task >> Can Start = True to the Filter Rules for your report? 

Previous, meaning a predecessor? If so, I've used this text mode from @AnthonyIm many times on a task report (thank you, Anthony!). It's from the Lateness of a Predecessor Task thread displayname=Predecessor Name and Actual Completion Datelistdelimiter=listmethod=nested(predecessors).liststextmode=t...

Ah ok, I see what you're looking for. I don't know how to do that straight from Workfront. I wonder if maybe @Doug_Den_Hoed__AtAppStore has an idea that would work for you - any thoughts, Doug?

We use the Last Viewed By: Name and the Last Viewed Date - these are native fields in the Report report type. Is that what you're looking for?