Product updates, improvements, and fixes in Stride
Future starts. When work can't begin yet, the field can now move a start date past the end of the update window instead of only leaving a note, with a note explaining what is holding the activity up. The finish moves with the start so the activity keeps the duration it had, and both dates turn purple to mark them as forecasts rather than recorded fact. Schedulers review them with the new Future Start filter.
Pushed dates stay in Stride — an activity with a pushed start is left out of the P6 export entirely, so downloading your updates is exactly as safe as before. If you also move the finish, Stride reads that as you stating how long the work now takes: only the updated remaining duration is exported, with no dates attached, so P6 picks up the new duration without touching your logic or constraints.
Activities that already started in P6 can't have their start pushed — the start has been recorded and it's the remaining duration, not the start, that expresses a delay there.
Moving a start that is already pushed opens with the note you wrote last time, so you can keep it, add to it, or replace it instead of starting from a blank box.
Turn it on per project in project settings under Allow Future Starts (off by default).
A finish moved on an activity whose start had been pushed was measured from the end of the update window rather than from the new start, inflating the exported remaining duration by the whole deferred gap. It is now measured from the pushed start, and a span that lands entirely on non-working days is floored at one working day so an unfinished activity can never export a zero duration (which P6 reads as complete).
Widening a baseline's update window past a date someone had pushed a start to left the activity showing a slip that was no longer in the future. Those forecasts are now withdrawn, along with any finish stated against them, and the activity goes back to needing an update on both ends.
Marking the finish of an activity with a pushed start could quietly record an actual start the user never chose. The finish now stands on its own on a pushed activity.
Accountability reminders counted an activity with a pushed start as still needing an update. They now agree with the schedule view.
In the Gantt chart, double-clicking an activity with a pushed start scrolled to where the activity was originally planned rather than to its bar. Jumping to one from the relationships panel had the same problem. Both now land on the bar.
The Gantt timeline could be sized too short to contain a pushed start or a pushed finish that ran past the end of the planned schedule, leaving those bars off the right edge of the chart entirely. The timeline now spans every date a bar can be drawn at.