Search Requests involving the RequestFeedback CustomField sometimes lead to Velocity null value errors in the logs

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 4.4.2, 4.5.0
    • Affects Version/s: 3.16.1
    • Component/s: Issue View
    • None
    • 2
    • Severity 3 - Minor
    • 7

      Issue Summary

      Intermittently, errors show up in the atlassian-jira.log mentioning null values for a velocity template tied to RequestFeedback custom field. The original trigger is a search request.

      The `Rating` and `Scale` parameters that the `request-feedback-root` velocity template expects do not always get passed along from the CF. This may be due to a user-permission/license check.

      Actual Results

      Exceptions of the following sort are thrown in the atlassian-jira.log file:

      /sr/jira.issueviews:searchrequest-excel-all-fields/temp/SearchRequest.xls [velocity] Left side ($nostar) of '>' operation has null value at com.atlassian.servicedesk:sd-request-feedback//servicedesk/customfields/request-feedback-root.vm[line 9, column 23]

      and

       

      /sr/jira.issueviews:searchrequest-excel-all-fields/temp/SearchRequest.xls [velocity] Left side ($rating) of '>' operation has null value at com.atlassian.servicedesk:sd-request-feedback//servicedesk/customfields/request-feedback-root.vm[line 3, column 23] 
      

      Workaround

      Currently there is no known workaround for this behavior. That said, the problem has only manifested itself in the logs. A workaround will be added here when available.

              Assignee:
              Kunal Kanojia
              Reporter:
              Seth Utecht (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: