Story Points per User on the same User Story
Asked by Emerson Henrique Cavalcante:

Is there any plan to allow assign Story points per User on the same User Story. Every now and then we have some user stories that more and 1 developer will work on, and somethimes we dont want to "split" the User Story into 2.

Today, we assign the Total User story points to finish it to the User story, but we can't see it on a Developer level. Also, sometimes we need 3 points for development due to complexity, but only 1 point for testing (on testing perspective, it may be a simple task). Today, we assign it as 4 points, but we can't split the effort based on the stage of the User Story.

Is that any plan to allow us to assign Sroty point per User Story and User assigned?


Answers:
author: Trudy Claspill
body: Hello [@Emerson Henrique Cavalcante](/t5/user/viewprofilepage/user-id/5596620)

Welcome to the Atlassian community.

What would you then expect to be able to do with that information, if you were able to split story points in that manner?

You could create Sub-tasks for each task that needs distinct story points. Story Points are not normally estimated at the Sub-task level, but you could add the field so that you could split story points per user/task.

However, Burndowns aren't based on sub-tasks. So you would not see story points being burned down based on the completion of sub-tasks.

comments: author: Emerson Henrique Cavalcante
body: Usually we have an average point each developer can work on each sprint, so when I'm planning and assigning Users Stories to the team during our meeting, it is really hard to calculate how many point each person has if we have to "manually" remove the testing points for each story, for example. We can survive, and we do this manually all the time, just to make sure we are not overloading anybody, but anyway, it woudl be great to have this automated.

We also have tried using tasks, but the points does not agreegate into the User Stories points, and also, as you pointed, are not included in the burndown.


author: Trudy Claspill
body: I'm not aware of any open Suggestion to enable multiple Story Point fields for issues with support for showing those distinct values in aggregated totals or as separate elements on the agile boards. And I'm not aware of any open Suggestion to modify the burndown charts to burndown based on anything thing other than the total Story points value when the story is transition to the "complete" status.

I am just a user of the Atlassian products, viewing the [public backlog](https://jira.atlassian.com/secure/Dashboard.jspa). You may want to reach out to [Atlassian Support](https://support.atlassian.com/contact/#/) directly to get their input on if such Suggestions exist.

You could create your own custom number fields to hold story points based on activity type, and Automation Rules to aggregate those values per story so that the total points are stored in the native Story points field for use in the agile boards and burndowns. If you are working with an agile board for a Company Managed Software project, you can add up to 3 additional fields to display on the cards, so you could have that information visible during your planning.


author: Emerson Henrique Cavalcante
body: That helps! I'll see if I do have access to create and manage those fields. Thanks for the support.


author: Trudy Claspill
body: Creating custom fields for Company Managed projects requires Jira Admin access. If you have it, then when you click the gear/cog button near your avatar you will see options like System, Projects, and Issues.

<https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-custom-fields/>

Adding fields to the cards on an agile board (supported only for boards for Company Managed Software projects) requires Board Administrator access for that board or Project Admin access for the Board Location project.

<https://support.atlassian.com/jira-software-cloud/docs/customize-cards/>


Tags: cloud

jira-cloud