Selected Assets object on the create issue screen may not be added to the created issue if the Assets custom field has multiple custom field context

XMLWordPrintable

    • Severity 2 - Major

      Issue Summary

      Assets object selected on create issue screen might be ignored if there are multiple custom field context configured for the Assets custom field. Even though the object can be selected based on the configured AQL, the object is not added and hence when the issue is created, the Assets custom field remains blank. For the Assets custom field that is required on the create issue screen, this means issue creation is not possible even though the object is selected on the screen.

      Steps to Reproduce

      1. Create an Assets IT Service Management project with sample data.
      2. Create another project with shared configuration of the project above.
      3. Configure the context of the Affected Server custom field and add a new context.
      4. In the new context, restrict it to one of the projects and use the AQL below.
        (objectType=Servers and Status=Running) or objectType=Computers
        
      5. Create an issue in the project created in step 1 with a Servers object selected on the Create issue screen.
      6. Create an issue in the project created in step 2 with a Computers object selected on the Create issue screen.
      7. Create an issue in the project created in step 2 with a Servers object selected on the Create issue screen.

      Expected Results

      All issues are created successfully with the expected object selected during the issue creation

      Actual Results

      The Computers object is not added to the issue without any error or warning anywhere in the log or UI. The other 2 issues are created with the selected Servers object as expected

      Workaround

      Currently there's no workaround to create an issue with the objects selected. However, it's possible to edit the screen and add the desired objects after issue creation.

      Another workaround is to upgrade JSM to 10.1.1 as it's not affected based on our testing. JSM 10 is a platform release and hence, please refer to the upgrade notes and release notes before upgrading.

      Versions Tested

      Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below: 

      Testing Requirements Version Affected Version
      Customers Reported Version 5.16.1 Yes
      Most Recent Bug-Fix Release 10.1.1 No 
      Previous Major Release    
      Most Recent LTS 5.12.14  No 
      Previous Supported LTS    
      Other Versions..  5.17.4  Yes
        5.11.3 No

            Assignee:
            Sam Xu
            Reporter:
            Michelle Chin (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: