The workflow for stories and tasks should be sequential. Here are some notes.

Tracking

represented as “Story”
Summary starts with “Sxx” , where xx is the number of the story with leading 0 if required
NO estimated time filled in
Fix Version is the Iteration. (NO Affects Version)
States:
- created (=open)
- in progress. Additional action: enter date into the release plan. The preliminary list of task has to be defined. Enter number of tasks to the release plan. Each of these tasks “is part of” the story.
- resolved. If all tasks are closed
- closed. If acceptance test passed. Additional action: enter date into the release plan. Enter actual number of tasks into the release plan. Also the sum of estimated and actual times.

represented as “Task”
Summary starts with “Sxx-Tyy” , where xx is the number of the story containing the task and yy the number of the task each with leading 0 if required
Fix Version is the Iteration. (NO Affects Version)
ESTIMATED TIME must be filled in. (Adaquate accuracy: quarters of an hour.)
States:
- created (=open)
- in progress. Additional action: assure that the estimated time is filled in. Enter the name of both developers to the Summary.
- resolved. If the work is done and all tests passed.
- closed. If the changes are checked into the CVS repository.

	Check for completness List mappings of XP/JIRA terms Make the text more readable.

SDA SE Wiki