Enable More Robust Capacity Planning through team and individual schedules

The way that capacity planning currently works is that you create a schedule with a static number that you label velocity, but isn't actually velocity. Each team's velocity is different and applying a blanket "each person does X hours or Y story points" is misleading as to what the team can actually accomplish.

So our capacity planning is always limited and more inaccurate than it needs to be and it limits some of our ability to realize value out of the capacity planning functionality.

Maintain the current functionality to allow to set a "default" for teams, but then allow teams to set their velocity for the team. Users should be able to either enter a single value, "My team's capacity is 35" or calculate based on a series of values I enter. "The previous 3 sprints, my team has completed 32, 29, and 36 story points. My average velocity for this is 32.3," and give the option to the round to round up or down ot the nearest whole number.

Additionally, on the user level, allowing users to enter days off (vacation days) to allow teams to further refine their velocity.

This is a gap with Jira functionality today, and add the functionality to do capacity planning at a lower level and longer term with greater flexibility and accuracy will go a long way to providing value.