Can we confirm this is going out to users? As far as I can tell, it is only targeting system admin access levels, but I'd like to be sure. -skye

In the setup area, there should be a way to opt out of "ads" that may pop up after login, or show up on the login screen.

haha yep, I should have been clear: I considered ASAP to be the logical choice on the parent. Outdented it shows one date and indented it shows the other. Recalc timelines doesn't fix it. I'll continue to wait on our ASE but if I bump into you at Leap I might show you. It's weird. -skye

for us it boiled down to how much users were in the tool. If someone's work consists of 5 hours of workfront work (tasks assigned in workfront) and 35 hours of meetings or "other", they are in there as 0.125 and I have a few (like... 2) people in there like this. 0.8 is also a number I have entered ...

hi, I have this question pending to support but I figured someone here might have a faster answer. If I have this situation, here are the resulting dates. Task 1, ASAP, predecessor=Task2 / fs / -10d = due 1/28/2019 Task 2, Must Finish On = due 2/10/2020 I think those are pretty correct (task 1 start...

Well, everything's a comparison of that date, either as a straight date or as a calculated field. For us it starts with being able to have a real, unique way to filter on that task, so whether that is a unique name ("Send email" becomes a phrase that no other tasks can use) or some other identifier ...

a parent task is any task with children (i.e. number of children > 0). If you don't want parent tasks, I would think you would filter on number of children = 0. Sorry - not sure why that wouldn't work for you but maybe if you share your error results it will clarify more. -skye

Just went in and took a look at this in preview: https://experience.workfront.com/s/article/2020-1-Beta-3-release-activity-869835725 (the first option, which reads " you can now indicate whether you want the results in the grouping to be expanded or collapsed by default when you display the list or ...

if the requestor is always second, this would be "Assignment users" | "role ID" | equals in your task report. The "Assigned to" "role ID" is for the primary assignee. But if there's no requestor listed... I assume you still put the role in the task? And then, what I haven't tested: if there's no one...

very true. It doesn't matter that a piece that we are creating might be done in 4-8 hours. What is being indicated here is that the piece has to pass through a certain number of hands (say, create - review - rework - finalize - distribute) and even if it only spends 15 minutes in each set of hands, ...