The following work items can be assigned to an agile team and added to that team’s backlog as stories, depending on the agile methodology the team is using:
Tasks or issues can be assigned to the team (and subsequently added to the team backlog) from anywhere in Adobe Workfront. For example, a single team might be assigned work assignments from multiple projects.
If you add multiple teams to a backlog item, the task or issue displays only on the primary team’s backlog. The primary team is the team first assigned.
You must have the following access to perform the steps in this article:
|Adobe Workfront plan*||
|Adobe Workfront license*||
Work or higher
|Access level configurations*||
Worker or higher
Note: If you still don't have access, ask your Workfront administrator if they set additional restrictions in your access level. For information on how a Workfront administrator can modify your access level, see Create or modify custom access levels.
Manage access to the project the story is on
For information on requesting additional access, see Request access to objects .
*To find out what plan, license type, or access you have, contact your Workfront administrator.
You can reorder stories in the backlog list by using the drag-and-drop method.
Go to the agile backlog where you want to reorder stories.
In the View drop-down menu, select the Backlog view or a custom view that contains the Order column.
If a task or issue has an agile team assigned and the project is not in a status that equates with Current, they do not display on the backlog. However, they do still affect the backlog count in the Order column.
Select one or more stories, then drag the stories to the order where you want them to appear in the backlog.
Because stories in a backlog vary in size, users can break them down into workable sizes for an iteration. Breaking a story down creates subtasks on the task that the story represents, and replaces the original task in the backlog. You can have a parent task or its subtasks assigned to an agile team, but you cannot have both assigned to a team simultaneously.
Consider the following limitations when breaking down stories:
To break down a story:
Go to the backlog that contains the story you want to break down.
Select the story you want to break down, then click Breakdown Story.
The Breakdown Story dialog box is displayed.
Specify a name and estimate for the story, and select whether the story is ready.
Click Add Story to create another story from the original story.
You can edit stories directly from the Stories or Issues tabs on the Backlog as you would edit any tasks or issues within a project in bulk, as described in Edit tasks in bulk in Edit tasks and Edit issues in Edit issues.
You can create new stories on the backlog by creating the story directly from the backlog, or by assigning an existing task or issue to an agile team.
When you create a story from the backlog, the story is created as a task or issue within a project. You cannot create a story from the backlog as an issue.
To create a story from the backlog:
Click the Main Menu icon in the upper-right corner of Adobe Workfront, then click Teams.
(Optional) Click the Switch team icon , then either select a new Scrum team from the drop-down menu or search for a team in the search bar.
Select Backlog from the left panel.
Do either of the following, depending on whether you want to create a task or an issue:
To create a task: Click Stories.
To Create an issue: Click Issues.
Click New Story or New Issue.
Specify the following information:
|Story Name||Type a name for the story.|
|Description||(Optional) Type a description for the story.|
|Ready||Select whether the story is ready to be added to an iteration. This setting is informational only. Stories can be added to an iteration regardless of the status of this setting.|
|Estimate||Specify a point or hourly estimate for the story. Estimates affect the burndown chart. The burndown chart for an iteration is accurate only if each story contains an accurate estimate. (If you provide a point estimate, you must have already designated in the team settings how many hours each point represents.)|
|Parent Project||Begin typing the name of the project where this story will be created, then click the name when it appears in the drop-down list.
The status of the project must be set to Current. If the status of the project is anything but Current, it is not displayed in the drop-down menu.
|Parent Task||(Optional) Begin typing the name of the parent task that this story is subordinate to, then click the name when it appears in the drop-down list.|
|Custom Forms||(Optional) Select any custom forms that you want to add to this story.|
Click Save Story.
You can assign a task or issue to an agile team. After it is assigned, the task or issue appears as a new story on the team backlog.
To assign a task or issue to an agile team:
Go to the backlog of the agile team.
Select the stories you want to move to an iteration or Kanban board, then click More > Move to.
If moving the story to a Kanban board, the Move Story to the Kanban Board is displayed.
If moving the story to an iteration, the Move Story to an Iteration dialog box is displayed.
Do either of the following:
For Scrum teams: In the Select Iteration field, select the iteration where you want to move the stories.
For Kanban teams: In the Select Kanban Board field, select your team Kanban board. (Kanban teams can have only one Kanban board.)
Click Move Story.
If you decide that your team is not yet ready to work on a story, you can move the story to the backlog.
For more information, see Move an agile story.
You can export one or more stories (including tasks and issues) directly from the backlog.
You export stories from the backlog in the same way that you export other data in Workfront, as described in Export data.