Permissions for moving bugs into a sprint

[Wayne Gibson]

Hi,

Is there a setting in JIRA Agile to allow users to pull items into a sprint based on the type of story.

We would like to allow anybody to pull a bug into the sprint, especially if it was raised within the curent sprint.

Thanks

[EddieW · Accepted solution]

There is not a specific permission based on issue type, only the general "schedule" issues permission that allows them to be added to sprints.

But addressing bugs in the manner you suggests sounds more like a Kanban board, OR stories being closed out prematurely (not properly tested)

[Wayne Gibson]

Hi,

Thanks for replyng.. The stories are being closed once all the testing and bugs are resolved.

Any bugs found whilst testing are logging in JIRA and flagged as blocking the story. This allows us to keep track of the issues found and then resolved.

But due to permissions, only certain people can drag them into the sprint.

It's a shame it isn't possible to create a bug as a sub task.

Any thoughts?

[EddieW]

Any bugs found whilst testing are logging in JIRA and flagged as blocking the story. This allows us to keep track of the issues found and then resolved.

That's my point.

It's not a defect/bug at that point, its just an unfinished story. Bugs occur _after_ the story has been released to users.

http://www.devx.com/architect/Article/46310

If that tester finds a problem with that story, this should not be considered a bug or defect. Sometimes teams will label this as such. Labeling this issues as defects before the sprint for that story is done, is confusing to the product manager. Because the story is not done, this cannot be a defect, the team has not said that we are ready for someone to use this. The team acknowledges that this might not be finished, that is why there is testing!

You should just create sub-tasks under the story if you want to block/track the effort to complete them while the story is still active. https://answers.atlassian.com/questions/123106/how-to-track-bugs-during-qa-of-a-user-story