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 targetproject 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.
Step 1: Configure Cross-Project Storage
Add theproject property to typeProperties in your risksheet.json:
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 thedocument property:
document is specified, new review work items are:
- Created in the target project as document work items
- Added to the specified document
- Positioned after the last existing review item of the same type
- Linked back to the source risk item via the configured link role
Step 3: Filter Reviews with Custom Queries (Optional)
Add aquery to control which reviews are retrieved and displayed:
Permissions and Access
For cross-project reviews to function correctly:| Requirement | Details |
|---|---|
| Read access | Users must have read access to both source and target projects |
| Write access | Users creating reviews need write access to the target project |
| Link role | The link role must support cross-project linking in Polarion |
| Work item creation | Creation permissions must be granted on the target project |
Example: Centralized Review Repository
For an organization where multiple risk analysis projects share one review project: Project A — FMEA Risk Analysis:CentralReviews project, organized in separate documents per source.
Troubleshooting
| Issue | Cause | Solution |
|---|---|---|
| Reviews not created in target project | project property value does not match | Verify the project ID matches the Polarion project exactly (case-sensitive) |
| Reviews appear in wrong document | document path incorrect | Check the document path format (e.g., "Space/DocumentName") |
| Cannot retrieve reviews from other project | Cross-project link not configured | Verify the link role supports cross-project links in Polarion admin |
| Permission denied on review creation | Insufficient write access | Grant write permissions in the target project for the reviewing users |
| Duplication error with cross-project tasks | Known issue in versions before 24.6.0 | Update to version 24.6.0 or later; as a workaround, remove the Task project column |
Verification
After completing configuration, you should now see:- New reviews created through Risksheet appear as work items in the target project
- If a document is specified, review work items are placed in that document in chronological order
- Bidirectional links connect the source risk items to the review work items across projects
- The Reviews column in Risksheet displays reviews from the target project correctly
See Also
- Configure Work Item-Based Reviews — base work item-based review configuration
- Set Up Review Process — overview of all review strategies
- Configure Cross-Project Linking — general cross-project linking setup
- Manage Cross-Project Resources — shared resources across projects
Sources
Sources
KB ArticlesSupport TicketsSource Code
WorkItemBasedReview.javaIReview.javaAppConfig.tsrisksheet.jsonCommentBasedReview.java