Playbook visibility conditions using Assets/CMDB object fields (cmdb-object-cftype) only match the first selected object when multiple objects are selected

XMLWordPrintable

    • 1
    • Minor
    • 1

      Issue Summary

      Playbook visibility conditions using Assets/CMDB object fields (cmdb-object-cftype) only match the first selected object when multiple objects are selected

      Steps to Reproduce

      1. Create an Assets/CMDB object field (e.g. "Software Application") on a JSM request type
      2. Create 3 separate Playbooks, each with a JQL visibility condition targeting a specific asset ARI:
        • Playbook A: "Software Application" = "ari:cloud:cmdb::object/ {workspaceId}/27092"
        • Playbook B: "Software Application" = "ari:cloud:cmdb::object/{workspaceId}
          /3468"
        • Playbook C: "Software Application" = "ari:cloud:cmdb::object/ {workspaceId}/XXXX"
      1. Create a JSM request and select all 3 assets in the field
      2. Open the Playbooks panel

      Expected Results

      All 3 Playbooks appear simultaneously — one per matched condition.

      Actual Results

      Only 1 Playbook appears. The others remain hidden despite their corresponding asset values being selected.

      Workaround

      Use a Jira Automation rule to copy the selected Assets object value into a parallel native multiselect field. Use that field in playbook conditions instead.
      Additional Notes

      • Native Jira multiselect fields (multiselect type) work correctly with this pattern — confirms the issue is specific to cmdb-object-cftype
      • REST API field schema confirms cmdb-object-cftype stores values as ARI strings in an array
      • JQL = operator on Assets fields appears to only evaluate the first ARI value in the array, not all selected values
      • First customer report — no existing JAC found
      • Related support case: PCS-3830782 (CoAction Specialty, JSM Premium)

              Assignee:
              Unassigned
              Reporter:
              Willian Sousa
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: