Add stories to an existing iteration
You can add stories to an iteration in any of the following ways:
-
From the backlog after the iteration is created, as described in the Move stories from the backlog to an iteration or Kanban board section in Manage the agile backlog
-
From the Details page of the individual task or issue
-
From a task or issue list
-
From a report
-
From a dashboard
Access requirements
You must have the following access to perform the steps in this article:
| table 0-row-2 1-row-2 2-row-2 layout-auto html-authored no-header | |
|---|---|
| Adobe Workfront plan | Any |
| Adobe Workfront license |
New: Standard or Current: Work or higher |
| Object permissions | Manage access to the project the story is on |
For more detail about the information in this table, see Access requirements in Workfront documentation.
Understand how adding stories affects task dates
By default, when you add an existing task to an iteration, the task’s Planned Start Date and Planned Completion Date are set as follows:
Task Planned Start Date
-
The task uses the iteration’s Start Date when:
- The project does not have a Planned Start Date set.
- The project’s Planned Start Date is before or on the iteration’s start date.
-
The task uses the project’s Planned Start Date when:
- The project’s Planned Start Date is after the iteration’s start date.
Task Planned Completion Date
-
The task uses the iteration’s End Date when:
- The project does not have a Planned Completion Date set.
- The project’s Planned Start Date is before or on the iteration’s Start Date or the Project’s Planned Completion Date is before or on the iteration’s End Date.
-
The task uses the project’s Planned Completion Date when:
- The project’s Planned Start Date is after the iteration’s Start Date and the project’s Planned Completion Date is after the iteration’s End Date.
You can configure individual Scrum teams to use the project dates by default, rather than the iteration dates. For information, see the section Configure how dates are applied when adding work items to an iteration in the article Configure Scrum.
Add a story to an existing iteration
You can add any task or issue to any iteration if you have Manage access to the project. Keep the following in mind when moving a task or issue to an iteration:
- If you add multiple teams, the task or issue can display only on one team’s iteration. This is the iteration you choose in step 3 below.
- If the task or issue is assigned to an agile team and moved to another team’s iteration, the team assignment does not change.
- If the task or issue is not assigned to a team, the task or issue is assigned to the team who owns the iteration.
- You can’t add parent tasks to the iteration. If you add any child tasks, the parent task appears on the Scrum board as a swimlane.
-
Open the task or issue you want to add to an iteration.
Or
Go to the project, report, or dashboard that contains the task or issue you want to add to an iteration. Then, select one or more tasks or issues. -
Click More
You cannot assign tasks or issues assigned to non-agile teams. -
In the Add To box, begin typing the name of the iteration, and select it when it appears in the list.
note note NOTE You can move a story from an existing iteration to a new iteration. -
Click Add.