> ## 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.

# Configure Multi-Project Setup

> Set up Nextedy RISKSHEET to load and manage work items across multiple Polarion projects, enabling cross-project risk analysis workflows.

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>;
};

## Prerequisites

* Risksheet installed and licensed on all participating projects
* At least one working Risksheet document in your primary project
* Knowledge of the project IDs for each Polarion project you want to connect
* Permissions to edit Risksheet configuration in each project

## Understand the Multi-Project Architecture

<Frame>
  <img src="https://mintcdn.com/none-17b4493f/-Icoak49xQVOW38R/risksheet/diagrams/guides/configuration/multi-project-setup/diagram-1.svg?fit=max&auto=format&n=-Icoak49xQVOW38R&q=85&s=a912583f48ebb3fbab91e15d3a1bf012" alt="diagram" style={{ maxWidth: "540px", width: "100%" }} width="540" height="300" data-path="risksheet/diagrams/guides/configuration/multi-project-setup/diagram-1.svg" />
</Frame>

<Steps>
  <Step title="Configure Cross-Project Upstream Columns">
    To display linked work items from another project, add the `project` parameter to your column's `typeProperties` in sheet configuration:

    ```yaml theme={null}
    columns:
    - id: upstreamRequirements
      header: Requirements
      type: multiItemLink
      typeProperties:
        linkRole: relates_to
        project: RequirementsProject
        linkTypes: requirement
    ```

    The `project` parameter accepts the Polarion project ID (not the display name) of the source project.

    <Warning title="Direct links only">
      The `project` parameter in `typeProperties` works for directly linked items only. If items are linked through intermediary work items in another project, those indirect links will not resolve automatically and require additional configuration.
    </Warning>
  </Step>

  <Step title="Configure Multiple Projects in a Single Column">
    To load items from several projects into one column, use Velocity snippets with `$config` properties in `typeProperties`:

    ```yaml theme={null}
    typeProperties:
      linkRole: relates_to
      project: $config.sourceProject1 $config.sourceProject2
      linkTypes: requirement
    ```

    Define the corresponding configuration properties at the project level so each deployment can specify its own source projects.

    <Warning title="Empty property values cause errors">
      When using configuration properties to define multi-project columns, empty property values after the `=` sign cause errors. Always ensure each property resolves to a valid project ID. Avoid referencing another configuration property variable as the alternative project value.
    </Warning>
  </Step>

  <Step title="Enable Cross-Project Item Creation">
    When a multi-project column links to items across projects, newly created items default to saving in the linked project. To create new items in the current project instead, set `createInCurrentDocument`:

    ```yaml theme={null}
    typeProperties:
      linkRole: relates_to
      project: ExternalProject
      itemType: task
      createInCurrentDocument: true
    ```

    | Property                  | Value             | Behavior                                                       |
    | ------------------------- | ----------------- | -------------------------------------------------------------- |
    | `createInCurrentDocument` | `true`            | New items saved in the current project and document            |
    | `createInCurrentDocument` | `false` (default) | New items created in the source project specified by `project` |

    <Tip title="Item creation scope">
      Setting `createInCurrentDocument` to `true` ensures new items are saved in the current project. Selecting a specific target project for new items (other than current or source) is not yet supported.
    </Tip>
  </Step>

  <Step title="Configure Cross-Project Downstream Tasks">
    For downstream mitigation tasks or verification activities stored in a separate project, configure the downstream column with the target project:

    ```yaml theme={null}
    columns:
    - id: mitigationTasks
      header: Mitigation Tasks
      type: taskLink
      typeProperties:
        project: VerificationProject

    dataTypes:
      task:
        type: task
        role: mitigates
    ```

    The downstream work item type is configured through `dataTypes.task.type` (see [Task Link Columns](/risksheet/reference/columns/task-link-columns)), while the `project` parameter in the column's `typeProperties` points the task lookup at the separate project.

    Work item deletion and unlinking across projects uses the `IdProject` format (`project/itemId`) internally. Risksheet handles this mapping automatically.
  </Step>

  <Step title="Verify the Configuration">
    After saving your changes:

    1. Open the Risksheet document in your primary project
    2. Verify that cross-project columns load items from the expected projects
    3. Try creating a new item in a cross-project column and confirm it saves to the correct project
    4. Check that linked items display their project-qualified IDs when hovering

    You should now see items from multiple projects rendered in your Risksheet columns.

    <Info title="Verify in application">
      In clustered Polarion deployments, configuration changes may not immediately propagate to all nodes. If the Risksheet displays differently across cluster nodes, refresh the page or clear the cache.
    </Info>
  </Step>
</Steps>

## Common Multi-Project Scenarios

| Scenario                               | Configuration Approach                                                            |
| -------------------------------------- | --------------------------------------------------------------------------------- |
| FMEA with external requirements        | `multiItemLink` column with `project` pointing to requirements project            |
| Shared risk components                 | Cross-project linking with `project` in `typeProperties`                          |
| Verification tasks in separate project | `taskLink` column with `project` targeting the verification project               |
| FHA loading existing functions         | Upstream `multiItemLink` with `project` and `itemType` set to load Function items |

<Warning title="Auto-population not supported">
  Risksheet cannot auto-populate rows with existing items from another project. The sheet starts empty and requires risk items to be created first, then linked to upstream items manually.
</Warning>

## See Also

* [Configure Upstream Traceability Columns](/risksheet/guides/columns/upstream-traceability) -- set up upstream link columns
* [Configure Downstream Tasks](/risksheet/guides/risk-management/downstream-tasks) -- downstream task configuration
* [Configure Cross-Project Linking](/risksheet/guides/advanced/cross-project-linking) -- advanced cross-project linking options
* [Manage Cross-Project Resources](/risksheet/guides/advanced/cross-project-resources) -- shared resources across projects
* [Work with Branched Documents](/risksheet/guides/integration/branched-documents) -- branching and variant management

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