CA PPM and Agile Central Integration - Milestone do not delete

Document ID : KB000113011
Last Modified Date : 04/09/2018
Show Technical Document Details
Issue:
When I delete Milestones from Agile Central they are being kept the CA PPM Project: <Project Name> - Properties - Main - Agile Summary page.

STEPS TO REPRODUCE:
  1. Create an Agile Central integration in CA PPM with “Create Direction: Agile Central to PPM”
  2. Create a new Project in CA PPM and navigate to the CA PPM Project: <Project Name> - Properties - Main - Agile Summary page
  3. Input the integration created in Step 1 within the “Agile System”
  4. Check the checkbox “Synchronize”
  5. Click Save
  6. Click on the “Actions” dropdown at the top right
  7. Click on “Synchronize Agile Central” to create the initiative from the Agile Central side
  8. Navigate to the Agile Central Environment
  9. Click on the Initiative ID to bring up the Initiative’s information
  10. Add one or two Milestones
  11. Click the Save button
  12. Navigate back to CA PPM and navigate to the Agile Summary page
  13. Click on the “Actions” dropdown at the top right
  14. Click on “Synchronize Agile Central” to sync the initiative from the Agile Central side
  15. Navigate to the Agile Central Environment
  16. Click on the Initiative ID to bring up the Initiative’s information
  17. Remove all Milestones currently added
  18. Click the Save button
  19. Navigate back to CA PPM and navigate to the Agile Summary page
  20. Click on the “Actions” dropdown at the top right
  21. Click on “Synchronize Agile Central” to sync the initiative from the Agile Central side
EXPECTED BEHAVIOR:
All Agile Milestones should be deleted from the CA PPM Project: <Project Name> - Properties - Main - Agile Summary page
 
ACTUAL BEHAVIOR:
The last Agile Milestone added from the Agile Central side is retained in the CA PPM Project: <Project Name> - Properties - Main - Agile Summary page
Environment:
CA PPM 15.4 and up
Resolution:
This is caused by Defect DE44016; currently there is no workaround for this issue and development is looking for a resolution.