Keep every Polarion project
in line with its template.
Keystone compares a project's configuration with its template or any other project, shows every difference file by file, and updates only what you choose. Every update can be reverted.
Templates drift. Projects drift further.
Every Polarion project starts from a template, then changes on its own: a workflow here, an enumeration there, a new custom field for one team. A year later nobody can say which projects still follow the standard.
Checking by hand means opening Administration screen by screen, project by project. Fixing it means retyping the same change in each project.
Four steps, and nothing is written until you say so.
Compare
Pick a project and what to compare it with: a template, a reference project, or a snapshot of the project itself. The comparison only reads.
Take
Differences are listed file by file, in the same sections as Polarion’s Administration. Each file opens to the exact items that differ. Every file starts on Keep; take the ones you want.
Update
Keystone writes only what you took, after a confirmation that states what it adds, changes and removes.
Revert
A restore point is captured before every update. One step takes the project back.
Everything a Polarion administrator needs to keep projects consistent.
See the whole configuration
One tree for any project or template: workflows, enumerations, custom fields, link roles, forms, queries, document types and LiveReport pages, named as Polarion names them. Search across all of it.
Compare anything with anything
Project against template, project against project, or a project against an earlier snapshot of itself. Each file opens to the items that differ.
Update only what you choose
Keep or Take, file by file, or take everything at once. LiveReport pages are added, replaced or removed the same way.
Restore and history
Every update is recorded with who made it and when. Restore a project to how it was before any update.
Snapshots
Pin a project’s configuration at a point in time, then compare against it whenever you need to.
Alignment across projects
Check many projects against their reference in one run and see at a glance how far each one has moved. Record which template each project follows, and check every project against its own.
Built for production Polarion, not a sandbox.
Configuration only
Keystone never reads or writes work items.
Read-only until you confirm
Comparing changes nothing. Update is the only action that writes.
A restore point before every update
Any update can be rolled back.
No silent overwrites
If someone changes the project after you compared, the update is refused, so their change is not lost.
Written the way Polarion writes it
Changes go through Polarion’s own API, and each one is checked after it lands.
Administrators only
Sign-in uses a Polarion administrator’s access token, kept in memory for the session and never stored.
Everything logged
Every update and every change to what a project follows is recorded.
The configuration that defines how your teams work.
| Area | What Keystone compares and updates |
|---|---|
| Work items | Types, custom fields, workflows (statuses, transitions, conditions, functions, signatures), read-only field rules, form layouts, filters and menus |
| Enumerations | General and type-dependent lists, with every option’s name, colour and icon |
| Traceability | Link roles and the rules for which types may be linked |
| Queries | Saved queries |
| Documents | Document types, document custom fields, document workflows |
| Pages | LiveReport pages, with a preview of layout and widgets |
Runs inside your network, next to your Polarion.
On your premises
No cloud service. Your configuration never leaves your network.
Two parts
A web app (a Docker or Podman container, or a Windows package) and a small extension installed on your Polarion server.
Licensed per Polarion instance
One licence covers the instance.
Works in the browser
Nothing to install on administrators’ machines.
The people who own the template.
- Polarion administrators who look after many projects built from company templates.
- ALM and tool owners who own the template and need every project to follow it.
- Process and quality leads in regulated engineering, such as automotive, medical devices and aerospace, who must show that each project runs the approved process.
See a project and its template side by side
In a short demo we compare a project with its template, take a few changes, update, and revert.
Polarion is a trademark of Siemens. Keystone is a product of XWARE, not of Siemens.