Skip to main content

​
Prerequisites

Before enabling cross-project reviews, ensure:
  • Work item-based review manager is configured (comment-based and approval-based reviews are limited to single projects)
  • Cross-project permissions are properly configured in Polarion
  • Target project(s) exist and are accessible to reviewers

​
Configure Cross-Project Review Storage

Edit your risksheet.json to specify where reviews should be created: 
{
  "reviews": {
    "reviewManager": "WorkItemBased",
    "typeProperties": {
      "linkTypes": "review",
      "linkRole": "reviews",
      "project": "REVIEW_PROJECT",
      "document": "REVIEW_PROJECT/reviews",
      "query": "NOT status:closed",
      "itemTemplate": "<span class=\"risk_reviews\"><b>$item.render().withLinks().htmlFor().forFrame()</b> by $item.fields().author().render().htmlFor().forFrame()<br/>$item.fields().description().render().htmlFor().forFrame()</span>"
    }
  }
}
Key properties:
  • project: Target project ID where review work items will be created
  • document: Specific document within the target project (format: PROJECT/DOCUMENT_ID)
  • query: Optional filter to show only relevant reviews (e.g., exclude closed reviews)

​
Use Dynamic Project Resolution

For flexible cross-project scenarios, use Velocity expressions to determine the target project dynamically: 
{
  "reviews": {
    "reviewManager": "WorkItemBased",
    "typeProperties": {
      "linkTypes": "review",
      "linkRole": "reviews",
      "project": "$doc.getReference().projectId()",
      "query": "NOT status:closed"
    }
  }
}
This configuration creates reviews in the same project as the reviewed work item.
For organizations with multiple risk projects, consider storing all reviews in a dedicated “Reviews” project. This centralizes review tracking and simplifies reporting across projects.

​
Cross-Project Review Workflow

diagram

​
Configure Cross-Project Permissions

Cross-project reviews require specific Polarion permissions:
  1. For reviewers: Grant “Create Work Items” permission in the target review project
  2. For risk managers: Grant “Read Work Items” permission in the target review project
  3. Link role visibility: Ensure the link role (reviews) is visible across both projects
Edit project.xml in both projects to allow the link role: 
<allowed-work-item-link-roles>
  <work-item-link-role id="reviews"/>
</allowed-work-item-link-roles>
If users cannot create reviews, verify they have “Create Work Items” permission in the target project, not just the source project containing the risk items. Permission errors are the most common cause of cross-project review failures.

​
Retrieve Cross-Project Reviews

RISKSHEET automatically retrieves linked reviews regardless of project location. The query property filters which reviews appear: 
"query": "project.id:REVIEW_PROJECT AND NOT status:(closed OR rejected)"
This example shows only open/approved reviews from the REVIEW_PROJECT.

​
Limitations

  • Comment-based reviews: Always stored on the work item itself—cannot be cross-project
  • Approval-based reviews: Use Polarion’s approval system—limited to the document’s project
  • Transitive linking: The project parameter filters direct linked items only. For multi-hop dependencies (Project A → Project A → Project B), use nested Risksheets or separate queries

​
Verification

After configuring cross-project reviews:
  1. Open a risk item in your RISKSHEET
  2. Click the review button to create a new review
  3. Navigate to the target project in Polarion
  4. Verify the review work item was created with the correct link back to the source risk
You should see the review displayed in your RISKSHEET with the reviewer’s name, timestamp, and content, even though the review work item resides in a different project.

​
See Also

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