Issue Statistics Gadget Crashes due to Unsupported Operator

XMLWordPrintable

    • 4.01
    • 1
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 06 September 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 – 06 September 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

      When you set a specific filter to be used in Issue Statistics Gadget, it doesn't work if you try to sort data by 'Total'. A error saying that the resource cannot be accessed is displayed.


      Selected sort by Total on filter options.


      An resource request attempt error is displayed.

      Also, the following appears in the atlassian-jira.log:

      WARN user 884x1554x1 mkvbh5 0:0:0:0:0:0:0:1 /rest/gadget/1.0/stats/generate [jira.jql.query.GenericClauseQueryFactory] The 'xxxx' clause does not support the = operator.

      Probably it happens because there are issues returned by the filter with a custom field that was setted as the statistic type of the gadget as NONE.

      WORKAROUND

      • You can append to your filter query AND <customfield> is not EMPTY. It'll avoid to catch issues with related custom field as null value.
      • Also, don't use the system null value to this related custom field (leaving it blank). Create a new value called "NULL" and set it as default custom field value instead.

        1. support_ss005.jpg
          support_ss005.jpg
          12 kB
        2. support_ss007.jpg
          support_ss007.jpg
          5 kB
        3. support_ss008.jpg
          support_ss008.jpg
          28 kB

            Assignee:
            Unassigned
            Reporter:
            Leandro Fanese Nunes [Atlassian]
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: