We generally assign a story to a developer and once its goes in QA if we reassign it to the tester than the story points are deducted from developers data and gets added to tester data.
Is there a way that a story can be assigned to one developer and tester together in order to get the right stats
Jira doesn't allow you to assign task to multiple users neither allow you to add more watchers (out of the box). Still its call as the best project tracking tool .. huh.
It's a better approach than multiple assignees - in the real world, that causes problems. I've never seen anywhere that allows many assignees that has not had massive problems with "I thought someone else was doing it"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No. Jira uses the assignee field to mean "This is the one single person currently responsible for the issue". I'm told one of the reasons it was written was because of the problems caused by allowing multiple assignees - it is inevitable that there will be cases of "I thought someone else named was doing it".
However, the assignee is a time based thing, that's why I emphasised the "currently". In general, there's an intention for an issue to be given to a developer, then when they finish, a tester, possibly some back and forth, and then closed, so the issue goes through a cycle of assignees.
There's also no harm in having many people owning or involved with an issue. Add a group-picker so you know the group that owns it. Or add fields to explicitly name the developer and tester (and others) for the whole lifetime. You can even get a bit clever with those - a common trick is to copy the tester from the field into the assignee when the developer clicks "ready for testing"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anthony,
There is an article titled How do I assign issues to multiple users that I found in JRASERVER-1397 that provides some suggestions on how you can implement this in your instance.
Also, take a look at the response from the Product Manager as it provides an explanation of why JIRA works this way.
Cheers,
Branden
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.