Is your feature request related to a problem? Please describe.
I'm always frustrated when the team does not complete what they have committed. In Quality-time, it is currently not possible to visualise stories that have been added during the sprint (after sprint start / after commitment). Presently, the only way to see this though the Burn Down Chart in Jira.
Describe the solution you'd like
A metric in Quality-time that shows scope creep. It should tell the user the number of issues OR the number of story points that have been added to the open sprint, after sprint start.
Describe alternatives you've considered
Alternatively, we could create a label 'committed-at-sprint-start' for every story after sprint start and create a JQL-filter for this. This will create a massive administrative burden for the team.
Is your feature request related to a problem? Please describe.
I'm always frustrated when the team does not complete what they have committed. In Quality-time, it is currently not possible to visualise stories that have been added during the sprint (after sprint start / after commitment). Presently, the only way to see this though the Burn Down Chart in Jira.
Describe the solution you'd like
A metric in Quality-time that shows scope creep. It should tell the user the number of issues OR the number of story points that have been added to the open sprint, after sprint start.
Describe alternatives you've considered
Alternatively, we could create a label 'committed-at-sprint-start' for every story after sprint start and create a JQL-filter for this. This will create a massive administrative burden for the team.