I'd like to second the point that Ingo added. The fact that the average velocity seems to include all iterations is problematic and leads to a lower-than-reasonable velocity if one of the iterations is the IP iteration.

Ideally it would be good if specific iterations could be marked as "do not include in velocity calculation", but I realize that might be tricky due to how Jira handles sprints. being able to always ignore the last iteration in a PI for velocity calculation would be a good first step.

And it would be perfect, if it leaves it to the RTE/Scrummaster if the IP-Iteration should be included or excluded.