Thanks again, Vic, From our "http://store.atappstore.com/product/excel-updater/">Excel Updater and "http://store.atappstore.com/workfront-merge-or-split/">Workfront Merge/Split work, I'm familiar with the repercussions of the various Task Constraints. However -- other than some excellent intros at LEAP -- I haven't delved into the Agile features much yet, so did some homework around what happens when (as you said) "a Task is moved to a Sprint". There's a good primer "https://support.workfront.com/hc/en-us/articles/216787328-Creating-an-Iteration">here , which highlights the main point of contention: namely, that the "end of the sprint" then drives (back) the (new) Planned Start Date of the Task that's been moved to the Sprint. And although it's possible to "https://support.workfront.com/hc/en-us/articles/218168448">Manage a Project in an Agile View , because "https://support.workfront.com/hc/en-us/articles/218168448#backlogs-and-iterations-are-not-used">Backlogs and Iterations are Not Used in such cases, I take it you are using Workfront to "https://support.workfront.com/hc/en-us/sections/203829917-Working-in-an-Agile-Environment">Work in an Agile Environment . When I think of moving Tasks from a backlog to Sprints, the chosen Tasks are from among a prioritized list of related Tasks that make sense to move as unit. But until your comment, hadn't pictured any (waterfall-ish?) ASAP-with-Predecessor-relationships on such Tasks; let alone that the Planned Start Dates for such items would be important to the Project Manager (and by extension, others). Would you kindly educate me by elaborating on the latter, in your case? Regards, Doug Doug Den Hoed - AtAppStore