How to configure the story points separated to dev points and QA points.

[swathi vasikarla]

Hello,

I remembered in my past company on Jira they have story points separated to Dev points and QA points. 

From where we can customize those fields ??

[Mark Segall]

Hi @swathi vasikarla and welcome to the community!

Let me start by saying that most teams measure velocity as a complete team rather than segregating out effort.  Thus story points are intended to be an estimation of the entire story effort so most teams come together during sprint planning to establish the estimation.  So, I would recommend to really evaluate your SDLC to see if it's possible to change the way things are viewed.  If the whole team is accountable for a story from open to close, you get better results from the team and thus velocity becomes a team measurement rather than individual.

Having stated that, I know that many teams encounter resourcing constraints where their QA team is sort of a pool of resources tied to multiple projects and may not do their part of the work in the same sprint as the dev team.  If this is your situation, rather than a separate estimation effort, I would create a separate linked story for the QA team to capture their estimation.  Then you can still take advantage of the native reporting.

[Trudy Claspill]

Hello @swathi vasikarla 

Welcome to the community.

You would need to generate separate custom fields for each of those. If you wanted that data summed and added to the built-in Story Points field, you would have to automate that process also. Jira does not support changing the native Reports or other functionality that leverages Story Points to instead leverage your custom Story Points fields.

If you are working with Jira Server/Data Center or Jira Cloud and Company Managed projects, only a Jira Administrator can make custom fields. If you are working with Jira Cloud and Team Managed projects, then the Project Administrator can make custom fields through Project Settings.