Hi, i have a question/suggestion for the story points segregation.
In my project we are facing same confusion and problem every time during the sprints.
The problem is that it's hard to understand how much DEV and how much QE points are estimated for the story, we are seeing summary only. But because each team referring to the total number it's unclear how the number was made off.
Will be much easier if Jira will segregate points somehow and make it visible on the "card face".
Example:
DEV points=x
QE points=z
Story points=x+z
Option #2
points 1=x
points 2=z
Total points=x+z
In a typical Scrum or Sprint, development and QE are part of the overall process and are not separated out. During story grooming would add the testing as part of the overall points for the story.
I can see, however, how this could cause confusion when one needs to track testing as a separate process outside of development. to address this you could use separate stories with different issue types for development and testing, and put them into the same sprint. Your workflow could include a post function to start the test story once the development story is marked "ready for testing" and, once the test story passes, use a post function to mark the development story as "done" when the test story is also moved to "done."
Of course, this is just one workaround, I'm sure there are other ways to manage it. In the meantime you can submit your enhancement request to Atlassian here: https://support.atlassian.com/contact/#/
-Scott
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Get started with Jira Service Management
These short, self-paced courses will help you get up and running in Jira Service Management in just 90 minutes.
Learning Path
Adopt ITSM practices with Jira Service Management
Use this path to build your IT Service Management knowledge and earn an Atlassian certification.
Setting Up ITSM Projects in Jira Service Management
This training series helps you get started in Jira Service Management quickly with the new ITSM project template.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.