Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-29200

Handle 'Method getHtml threw exception for reference $column in template templates/jira/issue/table/issuetable-issue.vm' errors more gracefully

    XMLWordPrintable

Details

    • 2
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 11 October 2019

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,

      Pawel Drygas,

      Jira Server Bugmaster

      Show
      Atlassian Update – 11 October 2019 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bugmaster

    Description

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      This error message appears often, in JIRA logs:

      Method getHtml threw exception for reference $column in template templates/jira/issue/table/issuetable-issue.vm

      This message is a symptom, not a root cause, from what I can tell. Here's what I found:

      1. I think this is the best description of it:

        If my search result contiains and issue for which myField is null/empty, then I get an error in the Jira search, as well as an exception in my Jira log. If modify my entry to have a non-Null/blank field in myField, then the Entry Navigator works as expected, with no errors returned.

      2. Looking through SAC tickets (note: these are not public), we have what would appear to be 45 different root causes, including NPEs, Illegal Argument exceptions, GreenHopper Rank exceptions, even OutOfMemory Errors. They apply to all different custom field types.

      Improvement Request
      In general I'm thinking this is an innocuous error, given that the true root cause is what error message appears below it (the NPE or otherwise), but perhaps it's worth implementing better error handling to indicate which custom field has the problem, and for which issue ID. This error is spamming the logs and is quite common.

      Workaround
      If you're a customer and are seeing this issue in your environment, look at the stacktrace error below this one to identify a true root cause.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-29200 Handle 'Method getHtml threw exception for reference $column in template templates/jira/issue/table/issuetable-issue.vm' errors more gracefully

          • Low - Low priority issues
          • Closed
          mentioned in

          Page Loading...

          Activity

            People

              Unassigned Unassigned
              jlargman Jeremy Largman
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: