Release 2.3.1

Protected built-in fields on RAIDD and OKRs.

On this page
Who is this for
Everyone

Released 4 November 2026. A hotfix (a small release that fixes problems quickly) after 2.3.0 (27 October 2026).

What's new?

Admins can no longer remove the built-in fields that RAIDD entries and Key Results depend on, so entries stay visible and Key Result progress stays correct.

Record types and fields

Eight built-in fields now show the lock that other protected fields have, so nobody removes them by accident.

  • Links on RAIDD entries. You can no longer remove the Links field of a Risk, Assumption, Issue, Dependency or Decision. People see an entry through the Program, Project, Staff member or Team it links to, so removing the field stopped people adding that type of entry and cut off access to existing ones. See Entities and custom fields.
  • Base, Current and Target on Key Results. You can no longer remove these three fields of a Key Result. A Metric Key Result works out its progress from them, and removing one set every Metric Key Result, and the Objectives above them, to 0%. See OKRs.

Good to know

  • On Administration → Entity & fields, a locked field shows a lock icon. In its Field actions menu, Remove field reads Protected field and Duplicate is greyed out. You can still rename these fields, move them and change their settings.
  • If an admin had already removed one of these fields, it comes back with its values when you upgrade.

Fixes

Fixes to built-in RAIDD and Key Result fields, so entries stay visible and Key Result progress stays correct.

We'd love your feedback

Have feedback or found a bug? Let us know. We are always improving Gembaa with your help.

Type a feature, a screen or a task, for example “allocation” or “share a view”.