Hi everyone,
I'm trying to determine whether this is expected behavior or a product defect in Enterprise Agile Planning(EAP) with the standard CWM integration.
Enviroment:
- ServiceNow Xanadu
- Enterprise Agile Planning (latest version)
- Standard CWM integration
Scenario
- A Program Increment(PI) is still planning.
- A child Sprint is started (this happens through the standard CWM integration)
- Later, a user attempts to start the parent PI (from EAP)
The update is aborted with the following error:
which simply checks whether any child iteration has: state=current, and abort the transaction.
After reviewing the OOB code, I also found another business rule that prevents multiple Current iterations for the same team by calling:
IterationMetadataImpl.hasCurrentIteration(current.eap_team).
However, I could not find any OOB validation that prevents a Sprint from becoming current while its parent PI is not started yet. This seems to creathe the following error:
- Sprint=current
- PI=planning
and then the PI can no longer be started becaue the business rule blocks the transition.
QUESTIONS:
- Is this the expexted behavior of EAP?
- Is there an OOB process that should prevent a Sprint from becoming Current before its parent PI?
- Has anuone encountered this with the standard CWM integration?
- Is there an official workaround or known PRB for this scenario?
Any guidance would be greatly appreciated. Thank you!
