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

Allow the use of other standard custom fields as placeholders in the filter issue scope AQL

XMLWordPrintable

    • 713
    • 183

    • 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.

    • Hide

      Hi Team 👋,

      First off, I want to apologise for the lack of updates on this feature request. We appreciate your engagement and understand how important this is to you.

      As you might have seen on other forums, we’ve been making significant investments in upgrading our platform to improve reliability and performance. This work is critical to laying a strong foundation for future development and ensuring a smoother experience for all users.

      Once these upgrades are fully released and stable, we’ll be in a much better position to revisit the roadmap and start addressing feature requests like this one.

      We still absolutely want to address this issue and acknowledge the frustration it may be causing. Thank you for your patience and understanding as we work through these priorities. Your continued feedback is invaluable, and we’re committed to keeping you updated on our progress.

      Thank you,
      Mohamed Hassan | Product Manager, JSM Assets

      Show
      Hi Team 👋, First off, I want to apologise for the lack of updates on this feature request. We appreciate your engagement and understand how important this is to you. As you might have seen on other forums, we’ve been making significant investments in upgrading our platform to improve reliability and performance. This work is critical to laying a strong foundation for future development and ensuring a smoother experience for all users. Once these upgrades are fully released and stable, we’ll be in a much better position to revisit the roadmap and start addressing feature requests like this one. We still absolutely want to address this issue and acknowledge the frustration it may be causing. Thank you for your patience and understanding as we work through these priorities. Your continued feedback is invaluable, and we’re committed to keeping you updated on our progress. Thank you, Mohamed Hassan | Product Manager, JSM Assets

      Issue Summary

      At the moment the only custom fields that can be used as placeholders are Assets custom fields and this feature would extend support for standard custom fields, like text fields

      Steps to Reproduce

      1. In your Assets field configuration use an AQL that references a custom field that is not an Assets custom field, ie. SimpleTextCustomField - customfield_xxxxx

      Expected Results

      Your search results reflect the values in that custom field. 

      Actual Results

      You don't get any results. 

      Workaround

      Set up an Assets field that mimics the value of that custom field, ie. an SimpleTextCustomField Assets field, and set that Assets field as the placeholder and also set up an Automation rule that populates that Assets field when the relevant custom field is changed. 

              e00fec873fe4 Sophia Do
              d80a14de5ac6 Kalanika Weerasinghe
              Votes:
              328 Vote for this issue
              Watchers:
              173 Start watching this issue

                Created:
                Updated: