This changes how a number is computed. Your charts can move without your data moving. Each change is named below with the reason for it.
Recording when people leave meant checking every place a salary or a person is counted. Two of them already disagreed with the rest of the product, so they now follow the same rule: a person counts only on the days they were employed, from their hire date to their last working day.
SP per engineer
Before: every sprint was divided by one fixed number, everyone in the company with a salary on record, whenever they joined or left.
Now: each sprint is divided by the people who were employed for at least one day of it, within the dates you selected.
What you will see: in sprints before someone joined or after someone left, the engineer count is lower, so SP per engineer goes up in those sprints. Where your team did not change, nothing moves.
Task cost in Task Details
Before: if a task had an assignee who was not employed on any day of the selected period, for example someone hired after it, the task was priced as if that person had been paid for the whole period.
Now: that person costs nothing in that period, the same as in team salary, lifecycle cost and project cost, which already worked this way.
What you will see: task cost can go down for tasks assigned to people outside their employment dates. Every other task is priced as before.
Why
A cost or productivity figure has to agree with itself across pages. Both changes make these two numbers use the same employment dates as every other salary and capacity figure in TheMetrics.