Moving of Jiras from unmapped status to mapped status resulted in churn

[WUPADRASTA SUBBARAO]

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

[Nic Brough -Adaptavist-]

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. 

[WUPADRASTA SUBBARAO]

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.

[WUPADRASTA SUBBARAO]

further, please review JSWSERVER-20184  and share your thoughts

[Nic Brough -Adaptavist-]

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)

[Nic Brough -Adaptavist-]

That issue is one that Atlassian should have closed as "working as intended" when it was first created.

If a status is unmapped, it can't be in the sprint.  It's nonsense to do it any other way.  

I suspect the issue is left open just as a reminder for Atlassian to make it more obvious what is happening - either by disallowing unmapped status, or putting something on screen to tell users "there are a load of issues missing from this board"

[WUPADRASTA SUBBARAO]

I must thank you for the deep dive into this issue and sharing your expert thoughts and inputs. I still feel that an alert should popup while moving a jira from unmpped to mapped status for an active sprint. It is a well known fact that when the story points or the sprint value is changed, a popup will show up with a message that 'scope the sprint will be affected'. This  is to warn the person making this change that not just the scope is going to be changed but the metrics would be impacted. Why this is not available while attempting to move a jira rom un-mapped to mapped? The user anyways knows that spring value or story point change would impact the scope and the metrics but still the alert is there. whereas many does not know(Though they are ought to know) that moving from unmapped to mapped would influence the metrics considering them as added to the sprint. This is where i believe the trigger or alert or a warning in terms of a pop up is necessary. 

[Nic Brough -Adaptavist-]

There's no warning pop-up because working this way is not a good practice and you are not expected to work in this poor manner.

The right way to work is to either have all the status mapped, or to not have a process that allows users to move an issue from an unmapped status to a mapped one.

[WUPADRASTA SUBBARAO]

the second one you suggested is what even i am suggesting i.e. a process that should not allow users to move an issue from unmapped to mapped status. as far as poor way of working is concerned, even changing the spring value or estimated efforts in between is not a right practice but for this we have the warning in the way of a pop up. In fact either moving the complete statuses to mapped too is a good advise. thank you. 

[Nic Brough -Adaptavist-]

Yep, you can prevent people from doing that by setting up the workflow so that it does not have the transitions that would let them move issues to from the unmapped status to a mapped on.