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
Also, take a look at the response from the Product Manager as it provides an explanation of why JIRA works this way.
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"
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs