How can stretch or non-committed stories be denoted so that metrics are accurate?

[Chandrasekaran R]

We have issues = user stories, tasks and subtasks that we plan for every sprint with Highest, high, medium and low priorities. Most of the medium and low were not getting done 100% for various reasons. But their incompleteness skews the metrics.  We want to bucket the medium and low priority issues into a category called stretch issues or non-committed issues for the sprint. Could someone help me how to classify them and solve this issue please?

Thanks

Chandra

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

If you have put a priority on the issues (Highest, high, medium and low) then you've done this "bucketing" already.  Just use the field in your reporting, it is the classification you are looking for.