Skip to main content
1

Open the Configuration File

Open the sheet configuration file attached to your Risksheet document. You can edit it through the configuration editor or directly as an attachment.
2

Define the Column Entry

Add a new object to the columns array in your configuration. Each column requires at minimum a bindings and header:
Risksheet column configuration defined in the risksheet.json document attachment
3

Configure Column Properties

Set the properties that control column behavior:
The first column showing the upstream traceability item linking a risk to its function or component
Level-3 items shown as children of the Risk item, representing downstream mitigation tasks
4

Group Related Columns

Use headerGroup to organize columns under a shared group header:
The group header height is controlled by headers.columnGroupHeader.height (default: 32 pixels).If you omit the type property, Risksheet automatically detects the type from the Polarion field definition. For standard Polarion fields like description, title, or severity, auto-detection works reliably. Explicitly set type when binding to custom fields or when you want to override the default rendering.
5

Control Read-Only Behavior

Certain columns become read-only automatically:
  • Columns with a formula property
  • Columns with a serverRender property
  • System fields: id, status, type, project, outlineNumber
  • Fields where Polarion permissions deny modification
To make a column explicitly non-editable:

Verification

Reload your Risksheet page after saving the configuration. You should now see the new column in the grid with the specified header text. Click on a cell in the column to verify it is editable (unless marked readOnly).

See Also

Last modified on July 10, 2026