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".
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/#/
Remember that time you realized it was possible to refresh your Jira data in Google sheets with just one click? What if we told you that you can now get the latest data with no clicks at all?! Zero! ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events