While there is no change in the sprint value assigned at the beginning of the sprint and no change in the estimated efforts to a jira still the churn metric is impacted because of moving the status from unmapped to mapped status. This seems to be incorrect
Welcome to the Atlassian Community!
It is not wrong. You have changed data in a way that means you are now reporting on things you were ignoring before.
When there is a change in the sprint value or the estimation of efforts i.e. story points, there is an alert that the scope of the sprint will be changed. If you mean that i have been ignoring this before on the unmapped to mapped status, why there is no alert or a trigger? please share your thoughts.
further, please review JSWSERVER-20184 and share your thoughts
You are changing the scope of the sprint when you move an issue into or out of it. That's half of the definition of scope change (the other is changing the estimate on an issue in the active sprint)
By definition, an unmapped status is not in a sprint. The mapped status are. So when you move an issue from an unmapped status to a mapped one, you are adding it to the sprint (or backlog)
It looks like you're new here. Sign in or register to get started.
