Laura, The reason you're probably getting that error is because you're putting these filters in for a NOTE report (which we've been using). (The same thing happened to me :-)). Cory is doing this from a "Project" report, so start with a Project report and then add the TEXT for a filter. (This is...

Thinking about the boolean question - I don't think there is one. What type of custom field are you using? They all have a value. So if you're using radio sets for a boolean question, it's not truely boolean as each radio set has a value (In this case, you assign it "Yes" and "No", but it could be "...

Yes, the field name is the label. You will need to add "DE:" in front of it. So if your custom field is called "This is a custom field", and your values might be "Hello", and "Goodbye", your Condition might be: DE:This is a custom field=Hello I'll check on the boolean question.

Laura, for my clarification, can you tell me what didn't work? From the Word doc you sent, based on the filters and what you said earlier, you get changes in status for projects, tasks, and issues. If you added a filter that said "where Note OjbCode is blank", you would just get Project status chang...

That's how you would filter them - by using the Note ObjCode. If you set it to "is blank", you get just Project Status changes. if you change it to "Task", you get Task changes, and if you set it to "opTask", you get Issue changes.

Laura, Thanks for sharing. I notice that your filters don't include where Note ObjCode is blank. Why aren't you getting issue and task status changes on your report as well? Also, I guess the Audit TYPE equal to "Status Change" or "Combined Entry" is not required since you've got the Audit Text ...

Angela, For those people who said they never received emails vs. those who do, you may want to check their email notification statuses (have they been turned off?). We have, as a company, turned off email notifications when being assigned to a task. We felt that would be way too many emails goin...

Actually, if there are predecessors assigned, I'd want to keep the logic they are doing now as if the task didn't start, regardless if the tasks were assigned to different people or not. the predecessors are there for a reason, and even if one was started, you'd still wouldn't want to ignore the pre...

Adam, Thanks for the reply. I don't understand why it would through out the predecessor logic once a task has started, but since it does, I will definitely submit a feature request. Based on what I've described below, it seems Workfront can't handle this real-world example. I'm hoping the Workfron...

David, Thanks for the ideas. You're correct that really there aren't true dependencies, but they are put there in order to get an estimated end date. In this simplistic example, there is only one resource on this project. You'd mentioned that you dont see how Workfront can be expected to estimat...