> ## Documentation Index
> Fetch the complete documentation index at: https://learn.nextedy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Work with Collections

> Understand how Nextedy RISKSHEET interacts with Polarion collections and configure workarounds for release-based filtering of risk items.

export const LastReviewed = ({date}) => {
  if (!date) return null;
  const formatted = new Date(`${date}T00:00:00Z`).toLocaleDateString("en-US", {
    year: "numeric",
    month: "long",
    day: "numeric",
    timeZone: "UTC"
  });
  return <p className="mt-10 text-sm text-gray-400 dark:text-zinc-500 not-prose">
      Last reviewed on {formatted}
    </p>;
};

<Info title="Feature Under Development">
  Full collection-awareness is a planned feature for Risksheet. The information below describes current behavior and available workarounds. Collection support is being prioritized as part of the product roadmap.
</Info>

## Current Behavior

Risksheet currently displays all work items belonging to a LiveDoc document regardless of Polarion collection context. When you open a Risksheet document within a collection, the grid shows the complete set of risk items rather than filtering to only those items relevant to the selected collection or revision.

This means that enterprise workflows relying on Polarion collections for release management will not automatically see collection-scoped views in Risksheet.

## Workaround: Document-Level Filtering

Until full collection support is available, use document-level filtering to restrict which items appear in your Risksheet views.

### Step 1: Organize Risk Documents by Release

Structure your risk analysis documents so that each document corresponds to a specific release or product scope:

1. Create separate LiveDoc documents for each release milestone
2. Keep risk items scoped to the document they belong to
3. Use the `document` property in `dataTypes` to restrict linked item loading to a specific document

```yaml theme={null}
dataTypes:
  task:
    type: measure
    role: has_measure
    document: Risks/Release-2.0-Measures
```

This configuration ensures that only mitigation tasks from the specified document appear in the Risksheet grid, effectively scoping your view to a single release.

### Step 2: Create a Saved View

1. Configure column visibility for the desired scope
2. Save the view with a descriptive name (e.g., "Release 2.0 View")
3. Share the view name with team members for consistent access

For details on creating saved views, see [Create Saved Views](/risksheet/guides/customization/saved-views).

### Step 3: Use Branching as an Alternative

For release-based workflows, consider using Risksheet's branching support as an alternative to collections:

1. Enable branching with `nextedy.risksheet.branchingSupport=true`
2. Branch your risk documents for each release
3. Each branched document maintains its own set of risk items at the correct revision

See [Work with Branched Documents](/risksheet/guides/integration/branched-documents) and [Configure Variant Management](/risksheet/guides/integration/variant-management) for detailed setup instructions.

<Tip title="Branching as a Collection Alternative">
  Document branching provides many of the same benefits as collection-based filtering -- revision-specific views, release scoping, and isolated editing -- without requiring full collection integration. This is the recommended approach for release management today.
</Tip>

## Read-Only Mode in Historical Revisions

When viewing Risksheet documents at a historical revision (whether through a collection or direct URL), Risksheet automatically enters read-only mode. The `readonly` property is forced to `true` when a non-empty `revision` value is set, preventing any edits to historical data.

This behavior applies to:

* Documents opened via collection at a specific revision
* Documents accessed with a `revision` URL parameter
* Baseline snapshots of risk analysis documents

<Warning title="No Editing in Historical Revisions">
  You cannot modify risk items when viewing a historical revision. If you need to edit items from a past release, work in the current (HEAD) revision of the branched document instead.
</Warning>

## Planned Collection Features

The following capabilities are planned for future Risksheet releases:

| Planned Feature            | Description                                                       |
| -------------------------- | ----------------------------------------------------------------- |
| Collection-aware filtering | Show only work items relevant to the selected collection          |
| Revision-correct display   | Display work items at the revision specified by the collection    |
| Collection-scoped search   | Restrict linked item search and suggestions to collection members |

## Verification

After configuring the document-level workaround:

1. Open a release-scoped Risksheet document
2. You should now see only the risk items and linked items scoped to that document
3. Verify that saved views filter the display as expected
4. Confirm that historical revisions open in read-only mode

## See Also

* [Work with Branched Documents](/risksheet/guides/integration/branched-documents) -- use branching for release management
* [Configure Variant Management](/risksheet/guides/integration/variant-management) -- manage product variants across releases
* [Create Saved Views](/risksheet/guides/customization/saved-views) -- define scope-specific column views
* [Configure Queries](/risksheet/guides/advanced/query-configuration) -- customize data filtering for release scopes

<LastReviewed date="2026-06-09" />