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

Details

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

    Description

      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. 

      Attachments

        Issue Links

          Activity

            People

              90325da67d46 Mohamed Hassan
              d80a14de5ac6 Kalanika Weerasinghe
              Votes:
              227 Vote for this issue
              Watchers:
              110 Start watching this issue

              Dates

                Created:
                Updated: