Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-11265

Changing Reference depth in Object Graph throws a JavaScript error and does not returns the right results

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Low
    • None
    • 4.22.1, 4.22.2, 4.22.6
    • None

    Description

      Issue Summary

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Create an Object Schema
      2. Create some Object Types
      3. Create some Objects
      4. Assign Inbound/outbound references among the Objects
      5. Open an Object detail page and click on the object name in the breadcrumb navigation
      6. Open Object Graph
      7. Open Configure panel (cog icon)
      8. Change the Reference depth value to more than 1
      9. Observe that the graph does not change (right results aren't shown)

      Expected Results

      No JavaScript exception is thrown in the console and the graph return right representation

      Actual Results

      JavaScript exception is thrown in the console and the graph never change from depth 1. The request is not even initiated.

      The below exception is thrown in Chrome developer tools:

      Uncaught Error: Minified React error #200; visit https://reactjs.org/docs/error-decoder.html?invariant=200 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
          at Object.t.render (batch.js?_v=81b2c65&baseurl-check-resources=true&healthcheck-resources=true&locale=en-US:63492:337428)
          at Object.so [as TreeGraph] (batch.js?_v=81b2c65&baseurl-check-resources=true&healthcheck-resources=true&locale=en-US:63492:1991919)
          at Object.RLABS.Object.Graph.initateTreeGraphIntoLegacy (batch.js?_v=81b2c65&baseurl-check-resources=true&healthcheck-resources=true&locale=en-US:58915:27)
          at child.changeReferenceDepth (batch.js?_v=81b2c65&baseurl-check-resources=true&healthcheck-resources=true&locale=en-US:59497:32)
          at mr (batch.js?locale=en-US:610:9385)
          at HTMLSelectElement.<anonymous> (batch.js?locale=en-US:610:9813)
          at HTMLSelectElement.<anonymous> (batch.js?locale=en-US:610:987)
          at HTMLDivElement.dispatch (batch.js?locale=en-US:174:3915)
          at HTMLDivElement.v.handle (batch.js?locale=en-US:174:2004)

      Note: In version 4.22.2 and 4.22.6 we get following similar error:

      Uncaught TypeError: Cannot read properties of undefined (reading 'stop')
          at HTMLDivElement.<anonymous> (batch.js?_v=40c2756&agile_global_admin_condition=true&baseurl-check-resources=true&healthcheck-resources=true&jag=true&jaguser=true&locale=en-US:59111:44)
          at HTMLDivElement.dispatch (batch.js?locale=en-US:179:3915)
          at v.handle (batch.js?locale=en-US:179:2004)
          at Object.trigger (batch.js?locale=en-US:189:23271)
          at u.event.trigger (batch.js?locale=en-US:412:3906)
          at u.fn.init.triggerHandler (batch.js?locale=en-US:189:23863)
          at batch.js?locale=en-US:1564:260
          at Function.cleanData (batch.js?_v=40c2756&agile_global_admin_condition=true&baseurl-check-resources=true&healthcheck-resources=true&jag=true&jaguser=true&locale=en-US:62795:324)
          at u.fn.init.empty (batch.js?locale=en-US:189:1692)
          at e.fn.<computed> [as empty] (batch.js?_v=40c2756&agile_global_admin_condition=true&baseurl-check-resources=true&healthcheck-resources=true&jag=true&jaguser=true&locale=en-US:104580:4157)
      

      Workaround

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

      Attachments

        Activity

          People

            Unassigned Unassigned
            4ef58f950c83 Andrea (Inactive)
            Votes:
            4 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:

              Backbone Issue Sync