Adjusting planned dates in an iteration

[#1]

When a task is in an iteration it assumes the planned completion date is the end of the iteration. When we have a month long iteration we frequently have tasks that will be completed at different points through out the iteration. We would like to be able to modify that start and end dates as long as it is within the iteration dates.

[#2]

This is critical for our team to realize the efficiency gains to be had. We collaborate with multiple teams, some work in sprints, some kanban, and some waterfall, and often times these tasks roll into a larger project template with strict deadlines due to the nature of the business. We need to control end dates as the sprint team task is a predecessor for others and a task being completed at the end of a sprint unnecessarily bloats the timeline. This restriction also prevents us from adding more teams to the system who continue to use Jira or other systems and are not connected to our flows.

[#3]

This is a huge painpoint for our team in Workfront, as our team entirely uses the agile sprint view. We've had to implement a lot of workarounds in the meantime and Kanban doesn't work for us for other reasons (aren't able to divide work into sprints or show hierarchy between parent and children tasks in our sprint board). This would make it much easier to collaborate with other teams on shared projects, would reduce stakeholder confusion on deliverable date sand would make it easier to recommend Workfront to new teams who haven't been onboarded as well.

[#4]

This is much needed, please update this, WF! Not every issue/task should need to be due the end date of an iteration, we need flexibility to change due dates to fall within the iteration timeframe. We are having to write in the due date we want in the task name, which is not only confusing for the assignee seeing 2 different dates but also for the PM not being able to change planned due dates easily.