Skip to main content

Prerequisites

  • Work item-based reviews configured (see Configure Work Item-Based Reviews)
  • A target Polarion project for centralized reviews
  • Cross-project link roles configured in Polarion
  • User permissions in both source and target projects
Cross-project review storage is only available with the WorkItemBased review strategy. Comment-based and approval-based reviews always store reviews on the work item in the current project.

How Cross-Project Reviews Work

When you configure a target project in the review typeProperties, Risksheet creates review work items in the specified project and links them back to the source risk item. Both the reviewed risk item and the review work item maintain bidirectional links that preserve revision information. diagram

Step 1: Configure Cross-Project Storage

Add the project property to typeProperties in your risksheet.json:
{
  "reviews": {
    "reviewManager": "WorkItemBased",
    "typeProperties": {
      "linkTypes": "reviewItem",
      "linkRole": "reviews",
      "project": "QualityReviews"
    }
  }
}
The project value must match the exact Polarion project ID of the target project.

Step 2: Store Reviews in a Specific Document (Optional)

To place review work items in a specific document within the target project, add the document property:
{
  "reviews": {
    "reviewManager": "WorkItemBased",
    "typeProperties": {
      "linkTypes": "reviewItem",
      "linkRole": "reviews",
      "project": "QualityReviews",
      "document": "Reviews/FMEA-Reviews"
    }
  }
}
When a document is specified, new review work items are:
  1. Created in the target project as document work items
  2. Added to the specified document
  3. Positioned after the last existing review item of the same type
  4. Linked back to the source risk item via the configured link role
The project and document properties support dynamic expression evaluation. You can resolve target locations based on the context of the reviewed item.

Step 3: Filter Reviews with Custom Queries (Optional)

Add a query to control which reviews are retrieved and displayed:
{
  "reviews": {
    "reviewManager": "WorkItemBased",
    "typeProperties": {
      "linkTypes": "reviewItem",
      "linkRole": "reviews",
      "project": "QualityReviews",
      "query": "NOT status:closed"
    }
  }
}
The query filter is applied during retrieval. Only review work items matching all criteria (type, link role, project, document, and query) appear in the Reviews column.

Permissions and Access

For cross-project reviews to function correctly:
RequirementDetails
Read accessUsers must have read access to both source and target projects
Write accessUsers creating reviews need write access to the target project
Link roleThe link role must support cross-project linking in Polarion
Work item creationCreation permissions must be granted on the target project
In clustered Polarion setups with separate servers, items cannot be linked across different Polarion server instances. Cross-project reviews only work within the same Polarion server.

Example: Centralized Review Repository

For an organization where multiple risk analysis projects share one review project: Project A — FMEA Risk Analysis:
{
  "reviews": {
    "reviewManager": "WorkItemBased",
    "typeProperties": {
      "linkTypes": "reviewItem",
      "linkRole": "reviews",
      "project": "CentralReviews",
      "document": "Reviews/ProjectA-FMEA"
    }
  }
}
Project B — HARA Risk Analysis:
{
  "reviews": {
    "reviewManager": "WorkItemBased",
    "typeProperties": {
      "linkTypes": "reviewItem",
      "linkRole": "reviews",
      "project": "CentralReviews",
      "document": "Reviews/ProjectB-HARA"
    }
  }
}
Both projects create review work items in the CentralReviews project, organized in separate documents per source.

Troubleshooting

IssueCauseSolution
Reviews not created in target projectproject property value does not matchVerify the project ID matches the Polarion project exactly (case-sensitive)
Reviews appear in wrong documentdocument path incorrectCheck the document path format (e.g., "Space/DocumentName")
Cannot retrieve reviews from other projectCross-project link not configuredVerify the link role supports cross-project links in Polarion admin
Permission denied on review creationInsufficient write accessGrant write permissions in the target project for the reviewing users
Duplication error with cross-project tasksKnown issue in versions before 24.6.0Update to version 24.6.0 or later; as a workaround, remove the Task project column

Verification

After completing configuration, you should now see:
  1. New reviews created through Risksheet appear as work items in the target project
  2. If a document is specified, review work items are placed in that document in chronological order
  3. Bidirectional links connect the source risk items to the review work items across projects
  4. The Reviews column in Risksheet displays reviews from the target project correctly

See Also

KB ArticlesSupport TicketsSource Code
  • WorkItemBasedReview.java
  • IReview.java
  • AppConfig.ts
  • risksheet.json
  • CommentBasedReview.java