Low Description
Issue Summary
When using Advanced Roadmap's old user experience, if a team has a user and you try to view the "Forecasted Velocity", Roadmap will fail to render the "Forecasted Velocity".
Steps to Reproduce
- Create a plan.
- Ensure that older experience is enabled.
- Click on Team.
- Add a user to the team on the plan.
- Click on the Velocity points.
Expected Results
Roadmap renders the "Forecasted Velocity".
Actual Results
Forecasted Velocity fails to be rendered an error is thrown from UI and also from atlassian-jira.log:
2020-06-26 17:05:58,424+0800 http-nio-8712-exec-10 url:/vicky/rest/jpo/1.0/velocityForecast username:vshanmugam ERROR vshanmugam 1025x1109x1 10bitj4 127.0.0.1,0:0:0:0:0:0:0:1 /rest/jpo/1.0/velocityForecast [c.a.r.c.r.provider.exception.DefaultExceptionMapper] java.lang.NullPointerException at com.atlassian.rm.jpo.core.scheduling.trafo.team.DefaultPointBasedTrafoTeam.getPlannedCapacities(DefaultPointBasedTrafoTeam.java:44) at com.atlassian.rm.jpo.core.scheduling.trafo.resource.DefaultAdjustedPointBasedResourceTransformer.createResources(DefaultAdjustedPointBasedResourceTransformer.java:86) at com.atlassian.rm.jpo.core.scheduling.trafo.team.DefaultTeamsTransformer.transformTeam(DefaultTeamsTransformer.java:134) at com.atlassian.rm.jpo.core.scheduling.trafo.team.DefaultTeamsTransformer.transformTeamsPointBased(DefaultTeamsTransformer.java:90) at com.atlassian.rm.jpo.core.scheduling.trafo.team.DefaultTeamsTransformer.transformTeams(DefaultTeamsTransformer.java:48) at com.atlassian.rm.jpo.core.scheduling.trafo.plan.DefaultSchedulingProblemTransformer.transform(DefaultSchedulingProblemTransformer.java:58) at com.atlassian.rm.jpo.core.scheduling.trafo.plan.DefaultSchedulingProblemTransformer.transformPlan(DefaultSchedulingProblemTransformer.java:49) at com.atlassian.rm.jpo.core.team.DefaultTeamSupplyForecastService.calculateTeamSupply(DefaultTeamSupplyForecastService.java:45) at com.atlassian.rm.jpo.rest.service.team.VelocityForecastRestEndPoint.getVelocityForecast(VelocityForecastRestEndPoint.java:32) ... 2 filtered
Workaround
- If you don't need the users in the team, removing them should work around this issue
- If you don't need to use the old user experience, switching to the improved user experience should work around this issue