Details
-
Bug
-
Resolution: Fixed
-
Medium
-
2015-10-26 Cloud, 7.0.4, 6.7.12, 7.0.5
-
None
-
6.07
-
Description
Summary
When viewing the release burndown report there's no data table rendered under the report and the js console has the following error:
The following JS error pops up in the UI
When using Firefox
Exception: TypeError: issueData104.estimateStatistic is undefined
Resource: http://<BaseURL>/s/a5c8bb12e9e9b1ccb06c5fea4e819a51-T/en_US53sh9d/70112/038344a3642fd2869d52d7530e380e51/eaa1da2e4cbe4b241293a0b4b70a38c1/_/download/contextbatch/js/greenhopper-rapid-non-gadget,gh-rapid,jira.project.sidebar,atl.general,atl.global,jira.global,jira.general,-_super/batch.js?agile_global_admin_condition=true&isAdmin=true&jag=true&jaguser=true&locale=en-US
Line: 21353
Column: 307
When using Chome
Exception: Uncaught TypeError: Cannot read property 'statFieldValue' of undefined Resource: http://<BaseURL>/s/43b93f60bd443d1f362bda76d725121e-T/en_US-vtgrqy/70111/b6b48b2829824b869586ac216d119363/6442100a4e80b2abad7eb96050d981e6/_/download/contextbatch/js/greenhopper-rapid-non-gadget,gh-rapid,jira.project.sidebar,atl.general,atl.global,jira.global,jira.general,-_super/batch.js?agile_global_admin_condition=true&isAdmin=true&jag=true&jaguser=true&locale=en-US Line: 107797 Column: 560
Steps to Reproduce
- Setup an Agile Board with estimation in Story Points
- Setup an Sprint such that some issue types do not have story points associated with them (ie some are estimated with time).
- Schedule and complete the sprint as normal.
- View the Release Burndown report.
Expected Results
The Release Burndown Report renders as normal.
Actual Results
The report fails, with the error Uncaught TypeError: Cannot read property 'statFieldValue' of undefined, and the below stack trace:
TypeError: Cannot read property 'statFieldValue' of undefined at Object.GH.tpl.reports.issueTable.renderIssueTableRows (http://sf-srv-sup-willienelson.office.atlassian.com:8702/ghs27407/s/95b7115a70e3442e7ebea4a2773faf96-CDN/en_US-jn4rf6/70111/b6b48b2829824b869586ac216d119363/d7d13e5ae078c2dac1fd9bebff4c20bf/_/download/contextbatch/js/greenhopper-rapid-non-gadget,gh-rapid,jira.project.sidebar,atl.general,atl.global,jira.global,jira.general,-_super/batch.js?agile_global_admin_condition=true&jag=true&jaguser=true&locale=en-US:89572:560) at Object.GH.tpl.reports.issueTable.renderIssueTable (http://sf-srv-sup-willienelson.office.atlassian.com:8702/ghs27407/s/95b7115a70e3442e7ebea4a2773faf96-CDN/en_US-jn4rf6/70111/b6b48b2829824b869586ac216d119363/d7d13e5ae078c2dac1fd9bebff4c20bf/_/download/contextbatch/js/greenhopper-rapid-non-gadget,gh-rapid,jira.project.sidebar,atl.general,atl.global,jira.global,jira.general,-_super/batch.js?agile_global_admin_condition=true&jag=true&jaguser=true&locale=en-US:89537:829) at Object.GH.tpl.reports.scopeBurndownBySprint.renderIssueTable (http://sf-srv-sup-willienelson.office.atlassian.com:8702/ghs27407/s/95b7115a70e3442e7ebea4a2773faf96-CDN/en_US-jn4rf6/70111/b6b48b2829824b869586ac216d119363/d7d13e5ae078c2dac1fd9bebff4c20bf/_/download/contextbatch/js/greenhopper-rapid-non-gadget,gh-rapid,jira.project.sidebar,atl.general,atl.global,jira.global,jira.general,-_super/batch.js?agile_global_admin_condition=true&jag=true&jaguser=true&locale=en-US:89647:87) at Object.GH.tpl.reports.scopeBurndownBySprint.renderIssueList (http://sf-srv-sup-willienelson.office.atlassian.com:8702/ghs27407/s/95b7115a70e3442e7ebea4a2773faf96-CDN/en_US-jn4rf6/70111/b6b48b2829824b869586ac216d119363/d7d13e5ae078c2dac1fd9bebff4c20bf/_/download/contextbatch/js/greenhopper-rapid-non-gadget,gh-rapid,jira.project.sidebar,atl.general,atl.global,jira.global,jira.general,-_super/batch.js?agile_global_admin_condition=true&jag=true&jaguser=true&locale=en-US:89636:52)
Workaround
- Check the JQL of the filter, to see which issue types are returned.
- Ensure all those issue types have the 'Story Points' JIRA Agile Custom Field.
Notes
Issue is caused by a bug in the soy template:
ReportIssueTable.soy
... <td class="ghx-right ghx-minimal ghx-nowrap" title="{$tooltip}"> {if $issue.estimateStatistic and $issue.currentEstimateStatistic and $issue.estimateStatistic.statFieldValue.text != $issue.currentEstimateStatistic.statFieldValue.text} {call .renderChangedEstimateIndicator} {param initialEstimate: $issue.estimateStatistic.statFieldValue.text /} {param currentEstimate: $issue.currentEstimateStatistic.statFieldValue.text /} {/call} {else} {$issue.estimateStatistic.statFieldValue.text} {/if} </td>
When attempting to render an issue without an $issue.estimateStatistic , $issue.estimateStatistic.statFieldValue.text cannot be read.
