Issue Summary

The client reached out because they have noticed that their average calculation was a bit off and they noticed that the IP sprint was being used for the average velocity calculation and they could like to have it removed.

Steps to Reproduce

IP sprints created in Align should not affect capacity or velocity.

If you ever wanted to know what sprints are being counted for a team's velocity figures go to Team-Teams-select the team and click on the Iterations tab.  The ones highlighted in yellow are being used to calculate the velocity (Screen Capture called “IP Sprint Count pertaining to Average Velocity”)

Sample Test 

In the below example there are 5 sprints being counted but instead of not counting the IP sprint It is counting the IP Sprint but not Sprint 6. The average Velocity here is = to 40.2 but the real average Velocity should be 35. (Screen Capture called “Broadcom | Calculating Average Velocity from Jira Align”).

What we currently do in Jira Align:

When Anchor Sprints are created for a PI, only the IP sprint will be pre-set as "IP Iteration".   The rest of the Anchor Sprints are "Standard Iteration (S)" 
As Team iterations are generated from the Anchor sprints, TDAD-22.1.4,  H2O-22.1.4 ...  are automatically set to "Standard Iteration (S)".  

Individual Team Iteration in Align has a "Type" configuration field, which its setting can be adjusted from "Standard Iteration" to "IP Iteration"

Expected Results

The average velocity calculation should not include the IP Sprint

Actual Results

The IP Sprint is being used for the average velocity calculation

Workaround

None