Parent/ child collisions are not detected if "change.conflict.currentwindow" = false but "change.conflict.relatedchildwindow = true" + "change.conflict.relatedparentwindow = true"

This defect has always existed in the code and is not a regression defect.

Steps to Reproduce

  1. Log in as an admin, and navigate to Change > Administration > Conflict Properties.
  2. Set the following properties:
    change.conflict.blackout = false
    change.conflict.currentci = false
    change.conflict.currentwindow = true
    change.conflict.relatedchildwindow = true
    change.conflict.relatedparentwindow = true
    change.conflict.mode = basic
  3. Upload the CIs attached (or create 3 related CIs).
  4. Create a new change, and enter the Configuration item (matching a CI uploaded or created).
  5. Under the Schedule tab, enter a planned start date and end date () that covers the weekend.
  6. Click the Check Conflicts related link, and note that Global Infrastructure conflicts are generated (the collisions related list should be added to the change_request form).
  7. Change the following property:
    change.conflict.currentwindow = false
  8. Note that no conflicts are generated even though parent/child properties are enabled.


There is no known workaround for this issue. If you are able to upgrade, review the Fixed In field to determine the versions that have a permanent fix to this issue.

Subscribe to this known error article (click the Subscribe button at the top of the article) to receive notifications when more information is available about this issue.

Related Problem: PRB600931

Seen In

There is no data to report.

Fixed In


Associated Community Threads

There is no data to report.

Article Information

Last Updated:2015-11-09 11:46:22