Uploaded image for project: 'Automation for Jira Server'
  1. Automation for Jira Server
  2. JIRAAUTOSERVER-505

As a customer, I'd like to search for objects in A4J configurations with the attribute I set as label

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Actions
    • 0
    • 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.

      Issue Summary

      Object searching in A4J is only possible with the Name attribute. In the case where an object type has no "Name" attribute but the label attribute is any other text attribute, it's not possible to find and select the desired objects from the drop-down list in A4J.

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Create an Assets IT Service Management project with sample data.
      2. Go to the schema created from the project above and go to the Attributes tab of the Business Services object type.
      3. Rename the "Name" attribute to "Services".
      4. Go to System > Automation rules, create a new rule.
      5. Select any trigger, for example Issue created.
      6. Select New action > Edit issue.
      7. Select Affected Business Service as the field to be edited.
      8. In the next field, start typing Billing Service.

      Expected Results

      The object with the label "Billing Service" is showing in the dropdown, available to be selected

      Actual Results

      No object is available. In the Developer Tools > Network tab, we can see that the Insight find objects REST API call is used for the object searching (and the search is with every existing object type as per JIRAAUTOSERVER-504). This means the search was done with an AQL like Name like billing, and since the name "Billing Service" is not a value of the "Name" attribute anymore, no object is shown.

      Workaround

      • Revert the change of the attribute renaming or create the "Name" attribute again and populate it with the desired values.
      • Alternatively, we can specify the Assets custom fields and objects to be assigned in JSON format as per Advanced field editing using JSON. Here's an example JSON text of setting an object (ITSMITSM-465) to an Assets custom field (customfield_10204).
        {
            "fields": {
                "customfield_10204": [{"key" : "ITSMITSM-465"}]
            }
        }
        

      Suggestion

      • Allow the search to be done with other attributes like the label attribute or "anyAttribute"

        1. 400 response when string includes a whitespace.png
          400 response when string includes a whitespace.png
          39 kB
        2.  workaround.png
          workaround.png
          22 kB
        3. not working.png
          not working.png
          58 kB
        4. screenshot-1.png
          screenshot-1.png
          570 kB

              Unassigned Unassigned
              8cdc82c96fd5 Yinon Negev
              Votes:
              4 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: