Update set not working correctly with Security Incident Response Task form views - Known Error

Update set not working correctly with Security Incident Response Task form views Description There are two domain separated instances source and target. Changes made to Security Incident Response Task form in source instance when retrieved via update set in target instance, don't update the form. It instead adds another section below the existing form section.

Steps to Reproduce

Requires 2 Kingston domain separated instances: On both source and target instance install the below 2 plugins 1. Security Incident Response 2. Domain Support - Domain Extensions Installer

A] Source Instance In global domain 1. Create an update set 2. Create a Security Incident Response Task (say Task1 src ) 3. Switch to any other OOB domain (say TOP/ACME) 4. Create another Security Incident Response Task (say Task2 src) 5. Add few fields to the form configuration (To find out difference between the layout of two tasks) 6. Navigate to the update set 7. Complete the update set and export the XML file

B] Target Instance In global domain 1. Create a Security Incident Response Task (say Task1 trg ) 2. Switch to same other domain as source instance (say TOP/ACME) 3. Create another Security Incident Response Task (say Task2 trg ) 4. Switch back to global domain 5. Retrive the source update set 6. Commit the update set 7. Open Task1 trg and Task2 trg Observe Task1 trg and Task2 trg

Expected behaviour: The target form should get updated with the added fields from the source instance.

Actual behavior: Another form section gets added below the existing task trg form section instead of updating it.

Workaround This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.