Burndown taking multiple developers for estimation

[Ian Miller]

When I put all my tasks into the sprint, and set the burn down to be based off time esitmates.

The chart just shows the total ammount of effort, and does not take into account the tasks will be assigned to muliple developers and some can be done simulanteously.

I've tried assigning the tasks to different developers, and this has no effect.

So a three week sprint, is actually coming out at 6 weeks, because we can't get the burndown to take into account the project has three developers.

[Ian Miller · Accepted solution]

What i mean is I have New Feature A assigned to developer A, and New Feature B assigned to Developer B, however when doing the burndown it is as if these features will be implemented one after the other when in fact the reality is Feature A and B will be implemented at the same time.

[Timothy]

JIRA has never adopted the concept of an issue assigned to multiple people. So yea, what you're doing is not possible. If you have 2 developers at 2 story points each, then the issue must have 4 story points.