Hi all,
We're planning an IFS Cloud upgrade from 24R2.2 to 26R1, skipping 25R1 and 25R2 as intermediate go-lives.
Could someone confirm:
1. Can the technical Release Update in Release Update Studio/Build Place be executed directly from 24R2.2 to 26R1 in one operation, or does it need to run sequentially through 25R1 and 25R2 first?
2. If sequential, does each intermediate release update need to be fully completed (and environment stable) before starting the next, or can they be chained back-to-back without a separate go-live at each stage?
3. Beyond the individual release notes, are there known issues specific to multi-release jumps we should plan for — e.g., EBR/database compliance prep, IFS Connect configuration resets, or custom lobby/report regressions?
Any guidance from partners or customers who've done a similar multi-release upgrade would be very helpful.
Thanks!