Skip to main content
Question

Upgrade a branch 25R2SU2 to 26R1SU2

  • August 12, 2026
  • 2 replies
  • 41 views
A
Do Gooder (Customer)
Forum|alt.badge.img+3

Hi, I’m coming to you because I would like to upgrade an unfinished release update branch 25R2SU2 to 26R1SU2. A delivery 25R2SU2 was created and applicated on a use place environment.

The master branch is actually on 25R1SU8 and I don’t want to modify it.

On build studio I ran an impact analysis and now I would like to request the release update, but this command/button isn’t visible on my portal.

Is this because my release update environment hasn't been finalized, a permissions issue, or some other reason ? 

Do you think I should delete my unfinished branch release update and begin a new with 26R1 ?
I follow this documentation https://docs.ifs.com/techdocs/ale/020_lifecycle/080_release_update_studio/020_request_release_update/010_create_sales_quotation/ but I’m actually limit.

If you have a solution, I'll take it!

2 replies

J
Do Gooder (Employee)
Forum|alt.badge.img+4
  • jomoes
  • Do Gooder (Employee)
  • August 13, 2026

Hi,

I believe the best way to handle this would be:

  1. To cancel the current Release Update: You can request it through a Support Case
  2. All Use Place environments updated with deliveries generated in the Release Update branch should be rolled back to the previous state. They would be in different release level so the Clone option is not supported, therefore they need to be restored from scratch.
  3. Start a new Release Update with the desired version.

I hope this helps.

ashen_malaka_ranasinghe
Superhero (Employee)
Forum|alt.badge.img+14

Hi ​@AHOSZEBESTA,

A key point is that "Request Release Update" is normally the starting step of a new Release Update process. Once a Release Update has already been requested/applied and a release-update branch exists, the portal typically progresses to the next stages (Apply Release Update, Impact Analysis, Environment Ordering, etc.) rather than offering "Request Release Update" again. The Release Update Studio workflow is designed as a sequential process where completion of one step enables the next.

The strongest clue is that you already have:

  • An existing 25R2 SU2 release update branch
  • A delivery created from it and deployed to a Use Place environment
  • An Impact Analysis already executed

In that situation, I would not immediately suspect a simple permission issue. In fact, internal Release Operations guidance states that if you want to start a new Release Update request, the existing Release Update process may first need to be aborted/cancelled, after which the user can return to Release Update Studio and request a new release update again. It also notes that certain actions require elevated permissions.

Before deleting anything, I would recommend checking:

  1. Whether the existing 25R2 SU2 Release Update process is still active in Release Update Studio.
  2. Whether the portal shows an Abort Process / Abort Release Update option.
  3. Whether the Release Update Summary indicates the process is still initialized, in progress, or partially completed.
  4. Whether your account has sufficient permissions to manage Release Update operations.
Find me on LinkedIn as Ashen Malaka: https://www.linkedin.com/in/ashen-malaka-ranasinghe/
Terms & ConditionsAccessibility statement