Is there a way to duplicate a story across a number of sprints and use the same story number?
2 answers
Hello Kelvin,
if you're talking of the work item number - it is unique - and duplicating your story will create a new work item with a new - unique - work item number.
Work item numbers are unique at server level.
Please also check this work item: Support more flexible Work Item identifiers (94065)
Thanks.
Eric.
if you're talking of the work item number - it is unique - and duplicating your story will create a new work item with a new - unique - work item number.
Work item numbers are unique at server level.
Please also check this work item: Support more flexible Work Item identifiers (94065)
Thanks.
Eric.
On a side topic, in an agile approach, a Story is supposed to be an amount of work that can be completed in one sprint. As such, you should not want to have storys being tracked across multiple sprints.
if you DO have work that needs to be tracked across multiple sprints, this is the use for Epic. it is a container for stories. The stories are tracked in the sprints, and the epic is tracked in the parent of the sprints, usually a release.
For us that is a quarterly iteration.
We added a Theme object to handle multiple release iterations, with multiple Epics.
if you DO have work that needs to be tracked across multiple sprints, this is the use for Epic. it is a container for stories. The stories are tracked in the sprints, and the epic is tracked in the parent of the sprints, usually a release.
For us that is a quarterly iteration.
We added a Theme object to handle multiple release iterations, with multiple Epics.