Next task due in a Project Report

Hi, if you are using predecessors, you can use “canStart” to filter for tasks that are next!

Hi ​@Tracy_Parmeter , the core challenge here is that text mode collections (listmethod=nested(tasks).lists with type=iterate) can't sort or limit to a single item as they return every task that matches your condition, in whatever order the collection provides, and there's no native .first equivalent that respects a date sort. That's why you're seeing all incomplete tasks come back unordered.

The suggestions above from Surya and Kellie will narrow the list to tasks that are ready to start (using canStart), which is a good filter, but they'll still potentially return multiple rows and won't guarantee the single earliest-due task.

For truly surfacing just the next task due, the most reliable approaches are:

The cleanest option is a calculated field updated via Fusion. A scenario can look at the project's incomplete tasks, sort by planned completion date, grab the first one, and write its name and due date to a project custom field. That field then displays as a clean single value in your report with no text mode gymnastics.

If Fusion isn't available, an alternative is to build a Task report instead of a Project report, filtered to incomplete tasks, sorted by Planned Completion Date ascending, and grouped by Project. The first task under each project group is your next task due. This doesn't give you a single project-report column, but it reliably shows the next due task per project and is fully native.

If you do want to stay with the collection column approach, you can combine Kellie's canStart filter with your date condition to at least reduce the noise, but be aware you can't force it to return only the single earliest one, that's the hard limitation of collections.