Your organisation already has words for these things. This add-on makes the product use them. Rename 36 root nouns across 10 modules and the change flows through every screen, including compound wording such as Resource Utilisation and Sprint Burndown Report. Twelve ready made industry sets ship with it, you can preview one before applying it, and you can edit any individual label afterwards.
- Installs
- Available
- Support
- Vendor Supported
- Trust
- Self-Hosted
Active deployments
Priority response
Your infra, your data
Screenshots
Key Features
36 Root Nouns
Project, Program, Task, Subtask, Assignee, Sprint, Backlog, Epic, Story, Milestone, Client, Team, Member, User, Role, Dashboard, Report, Resource, Risk, Document, and more.
Ten Modules
Nouns are grouped by the part of the product they belong to: projects, tasks, agile, epics, people, reports, risk, documents, test management, and general interface.
Compounds Handled
Renaming a root noun carries through the phrases built on it, so Resource Utilisation and Sprint Burndown Report follow the word you chose rather than staying behind.
12 Industry Templates
A default set plus law, education, defence, banking, BFSI, healthcare, manufacturing, construction, IT services, consulting, and government.
Preview Before Applying
A template preview fills the form in place with the proposed wording highlighted, so you see what the interface will say before anything is committed.
Explicit Save and Reset
Save, apply, reset, and cancel are deliberate actions rather than a form that quietly saves as you type. Reset returns the company to shipped wording.
Edit Any Single Label
Apply a template as a starting point, then override individual labels. A grouped, searchable list makes finding a specific piece of wording quick.
Clone to Custom
Clone any template into your own editable copy, adjust the singular and plural for each root noun, and apply it when it reads right.
Export and Import
Export a template as JSON and import it into another install, so staging and production say the same thing without anyone retyping it.
Built on the Translation Layer
Custom wording is merged into the translation catalogue, so every existing call resolves to your terminology. Templates are untouched and user entered data is never rewritten.
Per Company
Wording is stored per company, so on a multi-tenant install two tenants can call the same object completely different things on the same server.
Client Side Too
The active label map is published to the browser, so screens rendered on the client show the same wording as screens rendered on the server.
Role Permissions
Separate permissions for managing labels, managing industry templates, and reading the active label map, so wording changes stay with the people who should make them.
Catalogue Refresh Command
One idempotent command re-extracts translatable strings, adds any new ones without removing existing entries, regenerates every template, and re-applies each company's active template.
About this plugin
Why Label Customizer for Orangescrum?
Adoption stalls on vocabulary more often than on features. A law firm does not have projects, it has matters. A hospital does not have tasks, it has orders. A construction company does not have sprints. Asking people to translate in their heads every time they open a screen is a tax you pay forever, and this add-on removes it.
Rename the nouns, not the templates
36 root nouns across 10 modules cover the vocabulary of the product: project and programme, task and subtask, assignee and reporter, sprint and backlog, epic and story and milestone, client and team and member and user and role, dashboard and report and resource, risk, document, and test management wording. Change a root noun and the compounds built on it follow, so Resource Utilisation and Sprint Burndown Report do not get left behind.
Start from your industry
Twelve template sets ship with the add-on: a default plus law, education, defence, banking, BFSI, healthcare, manufacturing, construction, IT services, consulting, and government. Preview one and the form fills in place with the proposed wording highlighted, so you can read it before you commit. Apply it, then override any individual label that is not quite right.
How it works underneath
Custom wording is merged into the translation catalogue rather than swapped into the page after it renders. Every string the product already marks as translatable resolves to your terminology, on the server and in the browser, and user entered data is never touched. That is why nothing has to be edited in the templates and why an upgrade does not undo your work.
Per company, on the same server
Wording is stored against the company, so on a multi-tenant install two tenants can call the same object completely different things. Which template is active is tracked per company, and resetting returns that company to shipped wording without affecting anyone else.
Keeping the catalogue complete
As new screens are written, new strings appear. One idempotent command re-extracts the translatable strings, adds any new ones without removing existing entries, regenerates every template payload, and re-applies each company's active template. Run it in your release pipeline and coverage stays complete.
What's included
- 36 root nouns grouped across 10 modules
- Singular and plural wording per root noun
- Compound labels that follow the root noun you renamed
- 12 industry templates: default, law, education, defence, banking, BFSI, healthcare, manufacturing, construction, IT services, consulting, government
- Template preview that fills the form in place with proposed values highlighted
- Explicit save, apply, reset, and cancel actions
- Per label overrides on top of an applied template
- Grouped and searchable label management screen
- Clone a template into an editable custom copy
- Edit the singular and plural mapping of a custom template
- JSON export and import of a template between installs
- Reset a company back to shipped wording
- Overlay on the translation catalogue rather than a post render swap
- Active label map published for client rendered screens
- Per company storage with active template tracking
- Role permissions for managing labels, managing templates, and reading the label map
- Idempotent catalogue refresh command, plus separate payload generation and re-apply commands
- Multi-tenant company-scoped data isolation
Compatibility
Requires the Orangescrum Self-Hosted edition running PHP 8.2+, CakePHP 4.6+, and PostgreSQL 16. The plugin folder is LabelCustomizer and it is gated by the LABEL_CUSTOMIZER_ENABLED flag in config/constants.php. Custom wording is merged into the application translation catalogue at bootstrap, so core templates are never modified. Schema and seed data are installed through the standard install and upgrade flow. Multi-tenant aware, so every customisation, template, and active template record is company-scoped.
Installation
A self-hosted install takes a few minutes. Buy the add-on, drop the plugin into your plugins/ directory, run the migrations, and you're live.
- 1
Buy the add-on
Purchase the Label Customizer add-on from /self-hosted/pricing at $499/year per company, payable annually.
- 2
Drop the plugin into your install
Copy the LabelCustomizer/ folder into plugins/ on your self-hosted Orangescrum server.
- 3
Enable the feature flag and register the plugin
Add `define('LABEL_CUSTOMIZER_ENABLED', true);` to config/constants.php and register `LabelCustomizer` in src/Application.php with `routes => true, bootstrap => true`.
- 4
Run the migrations and seeders
Run `bin/cake migrations migrate -p LabelCustomizer` then `bin/cake migrations seed -p LabelCustomizer` to create the tables and load the root noun catalogue and the 12 industry templates.
- 5
Grant the permissions
Decide which roles may manage labels and which may manage industry templates. Reading the active label map is granted broadly so ordinary screens render correctly.
- 6
Preview an industry template
Open the Label Customizer settings screen, choose the template closest to your sector, and preview it. The proposed wording fills the form in place so you can read it before applying.
- 7
Apply, then fine tune
Apply the template, then override any individual labels that are not quite right. Clone the template into a custom copy if you want to keep your version as a reusable set.
- 8
Keep the catalogue current
Add `bin/cake refresh_label_catalog` to your release pipeline. It is idempotent and additive, so new wording is covered after every upgrade without losing what you set.
Frequently Asked Questions
Does this edit our templates or our theme?
▾
No. Custom wording is merged into the translation catalogue, so every string the product already marks as translatable resolves to your terminology. Nothing in the templates changes, which is also why an upgrade does not undo your renaming.
What happens to data people have already entered?
▾
Nothing. Only interface labels are affected. A project called Website Rebuild is still called Website Rebuild after you rename the noun Project to Matter. The renaming applies to the product's own wording, not to your content.
Can two companies on one install use different wording?
▾
Yes. Wording, the active template, and every override are stored against the company, so on a multi-tenant install two tenants can call the same object completely different things at the same time.
Can we rename anything at all in the interface?
▾
No. The catalogue covers the product's translatable strings, which is where the module nouns and the phrases built on them live. Text that is not part of that catalogue, such as content you entered yourself or wording inside a third party component, is not affected.
What if we only want to change a few words?
▾
Apply the default template or none at all, then override the individual labels you care about. The management screen groups labels by module and is searchable, so finding a specific piece of wording does not mean scrolling through everything.
Can we move our wording to another install?
▾
Yes. Export a template as JSON and import it on the target install. That is the usual way to keep staging and production saying the same thing without anyone retyping a list of labels.
Who is allowed to change labels?
▾
There are separate permissions for managing labels, managing industry templates, and reading the active label map. Owners always have access, and other roles get whatever you grant them, so terminology changes stay with the people who should be making them.
Ready to deploy Label Customizer on your own infrastructure?
Talk to our team about Orangescrum Self-Hosted Enterprise: your data, your servers, full control.