Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-11595

Insight Field filter issue scope does not work with custom field placeholder for IQL containing inbound/outbound references

XMLWordPrintable

    • 1
    • 12

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Summary

      Insight Field filter issue scope does not work with a custom field placeholder for IQL using inbound/outbound reference 

      Steps to Reproduce

      1. Setup a cascading Insight custom field Employee that will fetch the values based on another insight field Location
      2. Configure the Insight Field filter issue scope to use the below IQL and check the results: 
        object HAVING outR(objectType = "Location" AND Name = ${customfield_XXXX})

      Expected Results

      The feature work should work with the above IQL and fetches the objects with references to the 'Location' Insight field

      Actual Results

      The field with the IQL scope does not work.

      Workaround

      Use the below IQL to configure the Insight Field filter issue scope, the feature will work after that:

      object HAVING outR(objectType = "Location" AND Label = ${customfield_XXXX.label})

            [JSDCLOUD-11595] Insight Field filter issue scope does not work with custom field placeholder for IQL containing inbound/outbound references

            Mohamed Hassan added a comment -

            Hello Team 👋,

            I hope this message finds you well. We recently reviewed the behaviour reported in this ticket, and I wanted to clarify the situation.

            After a thorough review, we have confirmed that the behaviour in question aligns with our existing documentation and product specifications. This is an expected and intended functionality

            We understand that it might not align perfectly with the all users' expectations, and we are here to help address any concerns you might have. If this behaviour is impacting your workflows or if you have any further questions, please don't hesitate to reach out to me directly at mhassan@atlassian.com. Your feedback is invaluable to us 🙏

            Best regards,

            Mohamed Hassan | Product Manager

            Mohamed Hassan added a comment - Hello Team 👋, I hope this message finds you well. We recently reviewed the behaviour reported in this ticket, and I wanted to clarify the situation. After a thorough review, we have confirmed that the behaviour in question aligns with our existing documentation and product specifications. This is an expected and intended functionality We understand that it might not align perfectly with the all users' expectations, and we are here to help address any concerns you might have. If this behaviour is impacting your workflows or if you have any further questions, please don't hesitate to reach out to me directly at mhassan@atlassian.com. Your feedback is invaluable to us 🙏 Best regards, Mohamed Hassan | Product Manager

            Cristian Iorio added a comment -

            Come on, I really cannot understand how it is necessary to understand the impact of this malfunction for such a long time.

            It is not a bypassable behavior for Asset users. This problem can compromise the entire user experience.

            Cristian Iorio added a comment - Come on, I really cannot understand how it is necessary to understand the impact of this malfunction for such a long time. It is not a bypassable behavior for Asset users. This problem can compromise the entire user experience.

              90325da67d46 Mohamed Hassan
              vchoo Vivian C
              Votes:
              24 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: