Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-16002

Issue scope filter placeholder only works in Create screens

XMLWordPrintable

      Issue Summary

      When using a placeholder of type ${pid.id} in the issue scope filter for an Assets custom field, the subsequent object search only works correctly when creating a Jira issue. When editing, no matches are found.

      Steps to Reproduce

      1. Create a project of any type
      2. Choose any object type and add an attribute of type Project called "Id"
      3. Create an object of the above type
      4. Make sure the Project attribute is set to the project created earlier
      5. Create a custom field of type Assets Objects and add to the relevant screens
      6. Edit the custom field Assets configuration
      7. Select the schema
      8. Add the following filter scope: objectType = <objectTypeID_of_the_object_type_from_earlier>
      9. Add the following filter issue scope AQL: "Id" = ${pid.id}
      10. Create a new issue
        1. Observe that the filter works correctly
      11. Edit the issue
        1. Observe that no matches are found

      Expected Results

      The behavior is consistent across different actions.

      Actual Results

      The filter only works in the Create screen.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available.

          Form Name

            [JSDSERVER-16002] Issue scope filter placeholder only works in Create screens

            Vilim Berger added a comment -

            Workaround Suggestion:

            1. In the "Project" object, add a new "Project" type attribute alongside the existing "Id" attribute (e.g., name it "Project Reference").
            2. Populate this new attribute with the same project value that corresponds to the project's ID in the "Id" attribute (or consider using only the newly created attribute instead of "Id").
            3. Update the "Filter issue scope AQL" as follows:
              • If using only the newly created attribute:
                "Project Reference" = currentProject()
              • If using both attributes:
                "Id" = ${pid.id} OR "Project Reference" = currentProject()

            I hope this helps.

            Vilim Berger added a comment - Workaround Suggestion: In the "Project" object, add a new "Project" type attribute alongside the existing "Id" attribute (e.g., name it "Project Reference" ). Populate this new attribute with the same project value that corresponds to the project's ID in the "Id" attribute (or consider using only the newly created attribute instead of "Id" ). Update the "Filter issue scope AQL" as follows: If using only the newly created attribute: "Project Reference" = currentProject() If using both attributes: "Id" = ${pid.id} OR "Project Reference" = currentProject() I hope this helps.

              344ed8f58f8f Alec Bignell
              braymundo Bruno Raymundo
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: