Skip to main content
Next release

Disable any development in Finalized branches

Related products:Software Factory
  • July 15, 2026
  • 3 replies
  • 34 views

Raymond Gerritsen
Thinkwiser
Forum|alt.badge.img+1

When a finished branch gets merged to it's origin (non-reciprocal). It becomes finalized and, depending on selection, archived. Further merging into and from this branch is thereafter no longer possible. Yet, active development is still possible in a finalized branch (even after unarchiving). Wouldn't it make sense to completely lock development in a finalized branch as well? 

I have experienced a scenario where an unsuspecting developer was actively developing in a finalized branch (without knowing it was a finalized branch) and then find out way too late all of his work is for naught.

3 replies

Arie V
Community Manager
Forum|alt.badge.img+12
  • Community Manager
  • July 16, 2026
Updated idea statusNewNext release

Arie V
Community Manager
Forum|alt.badge.img+12
  • Community Manager
  • July 16, 2026

@Raymond Gerritsen Had a quick chat with ​@Mark Jongeling and he’ll include a change with Platform version 2026.2.12 (next release) that ensures that Branch access is set to ‘Read only’ for all Users when a Branch is set to status ‘Finalized’. That should significantly reduce the risk that someone is unexpectedly developing in a finalized branch!

 


Raymond Gerritsen
Thinkwiser
Forum|alt.badge.img+1

@Raymond Gerritsen Had a quick chat with ​@Mark Jongeling and he’ll include a change with Platform version 2026.2.12 (next release) that ensures that Branch access is set to ‘Read only’ for all Users when a Branch is set to status ‘Finalized’. That should significantly reduce the risk that someone is unexpectedly developing in a finalized branch!

 

Awesome, thank you for the quick response and resolution!