Hi Jill, If you have a task report, each row that is returned will be a task, and everything has to relate to that task. So you can pull 'down' information from the project, program and/or portfolio, as there is a direct relationship with the task. If you get funky with collections, you can pull 'up' information that has a many to one relationship with the task (assignee's other than the primary assignee, hours logged, issues related to the task etc). So normally, you'd need some connection between the two tasks (like the task is a sub-task of 'Mail Date', so you can refer to the Parent, or 'Mail Date' is a predecessor of the task). But we can stretch collections a little bit. So collections are when there are an unknown number of things attached to what you're reporting on. But you can actually traverse the hierarchy with a collection. From the task report, I can go to the project and pull the task collection (every task in the project), filter it to just the one I want, and report on that. The following should work for you: displayname=Mail Date listdelimiter= listmethod=nested(project.tasks).lists textmode=true type=iterate valueexpression=IF({name}='Managing Issues', {plannedCompletionDate}) valueformat=HTML Note that normal collection behaviour is to put something between every object in the list - even if it doesn't return data for it. So you would expect a common or a line break per task in the project, even if it only finds one date. To circumvent this, I'm using an entity number (0 width space) as the delimiter. Barry Buchanan Work Management Australia