Using Agile, how should JIRA stories be assigned throughout the workflow?

[Bryan Riley]

I have used JIRA in the past, but never for true Agile work. In the past when creating a normal 'jira' request, it would be assigned to the actual developer that is working on the issue.

Now that we're using JIRA w/GreenHopper, our stories are always assigned to the product owner. Developers are then creating subtasks for each piece of development.

It almost seems like the actual story should be getting assigned to a developer when it gets pulled into a sprint. Then the developer could assign to QA. Then QA could assign back to product owner for verification.

Does someone have documentation on a best practice for the actual assignment of stories?

[K Kelly]

We do utilize Jira and Greenhopper for our sprints. Our user stories are initiated by the product owner.

Once they are assigned to the sprint and prioritized, each team member creates their applicable subtasks.

The user story is initially assigned to the developer; once all their subtasks are complete and it is in the build, ready for QA, they assign it to the QA. It remains in QA's queue until it has met the done criteria. Once it meets the done criteria, it is resolved and put back into the Product Owner's queue.

Once the product owner accepts the user story as done, then it is closed.

That's at least how our process works.

[Deepak Purushothaman]

User stories should never be assigned. Scrum is a pull mechanism not push. The developers should volunteer and pick up stories. It needs to be a self organizing team.