Issue Summary

Burndown report at a team level errors with "Whoops - Get me out of here" when atleast one of sprint of the team has the actualEndDate as null

Steps to Reproduce

1. Identify sprints that have the actualEndDate as null using the API call - https://<JA_URL/rest/align/api/2/Iterations?$filter=actualEndDate eq null
2. pick one sprint from the above output.
3. note the releaseID and teamId based on above output
4. Note the PI name corresponding to the releaseID from the Jira Align console
5. Browse to corresponding team on the Jira Align Console matching the above noted teamId
6. Browse to Reports > Burddown and choose the PI noted above
7. Notice the error "Whoops - Get me out of here"
8. Notice the ASP logs error as below:

"Level":"Error","MessageTemplate":"SQLError","RenderedMessage":"SQLError","Exception":"System.FormatException: Failed to convert parameter value from a String to a DateTime. ---> System.FormatException: String was not recognized as a valid DateTime.\r\n   at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)\r\n   at System.Convert.ToDateTime(String value, IFormatProvider provider)

Expected Results

• Burndown chart should be generated even if the actualEndDate is missing.

Actual Results

• Burndown chart is not generated when the actualEndDate is missing on the sprint.

Workaround

Currently, there is no known workaround for this behaviour. A workaround will be added here when available