The usage scenario is:
How would one do this? What are some implications from reopening the original Jira issue rather than creating a bug and pulling it into a new sprint?
Thanks,
The correct solution is to create a new Bug and link it to the original Story.
However, if you really must reopen the story, then you will need to edit the Story workflow to create a transition, either to a new state of Reopened, or back to an existing state. This transition should also be made to clear the "resolution" field (via workflow post-conditions.
I agree upon the correct approach. But since Scrum teams can define their working agreement and go through a learning cycle ...
And understood with respect to the work flow changes.
Thx
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"The development team would like to reopen the issue rather than create a bug."
But why? Reopening issue closed in the last sprint would result in false reports because it would add e.g. closed story points value to both sprints.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
agree that opening a bug on a "released" feature is the correct approach. That said if you wish to reopen an issue you simply need to have a transition from the closed status back to To Do or whatever status you want. Be sure to have a post-function that clears the Resolution field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.