Our metrics dashboard widget is not rendering requirement-to-test traceability links for compliance reporting. The DOORS Next REST API endpoint returns trace data, but the dashboard shows empty cells where bidirectional links should appear.
I’ve verified the REST API query returns valid trace artifacts:
GET /rm/publish/resources?oslc.where=dcterms:type="Requirement"
&oslc.select=dcterms:identifier,oslc_rm:trackedBy
Response: 200 OK with trace URIs in trackedBy field
However, the dashboard widget artifact type mapping doesn’t recognize these links. User role permissions on trace artifacts seem correct - I can view traces in DOORS Next directly. Is there a cache invalidation issue or missing widget configuration for bidirectional traceability query filters?
The widget is configured for artifact types ‘Requirement’ and ‘TestCase’, but I’m not sure about the relationship types. Should I be explicitly mapping ‘oslc_rm:trackedBy’ and ‘oslc_rm:tracks’ as bidirectional pairs? Also, the cache refresh timing seems inconsistent - sometimes links appear after 10-15 minutes, other times they don’t show at all even after hours.
Let me provide a complete solution addressing all the configuration gaps:
1. DOORS Next REST API Endpoint Configuration:
Verify your REST API query includes both trace directions. Update your endpoint to explicitly request bidirectional links:
GET /rm/publish/resources?oslc.where=dcterms:type="Requirement"
&oslc.select=dcterms:identifier,oslc_rm:trackedBy,oslc_rm:tracks
2. Bidirectional Traceability Query Filters:
In the dashboard widget configuration, add both relationship predicates under ‘Trace Link Types’:
- Forward:
oslc_rm:trackedBy (Requirement → Test Case)
- Backward:
oslc_rm:tracks (Test Case → Requirement)
The widget needs both directions explicitly configured to render bidirectional links.
3. Dashboard Widget Artifact Type Mapping:
Navigate to Dashboard > Widget Settings > Artifact Type Mapping:
4. User Role Permissions on Trace Artifacts:
As mentioned by security_admin, grant the dashboard service account the ‘Traceability Reader’ role:
- Project Area > Permissions > Service Accounts
- Add dashboard service account to ‘Traceability Reader’ role
- This provides READ access to link artifacts across all types
Alternatively, if using personal accounts, ensure each user has ‘Link Reader’ permission in their project role.
5. Cache Invalidation and Refresh Timing:
Enable trace-aware cache invalidation:
- Dashboard Widget > Advanced Settings > ‘Trace Link Change Monitoring’ = Enabled
- Set ‘Cache Refresh Interval’ to 300 seconds (5 minutes) for near-real-time updates
- Enable ‘Force Refresh on Link Modification’ to invalidate cache when traces change
After applying these configurations, restart the dashboard service to clear existing cache. The widget should now display requirement-to-test traceability links correctly with consistent refresh behavior. Test by creating a new trace link and verifying it appears within the configured refresh interval.
One more thing about cache timing - the dashboard widget cache invalidation is controlled by the refresh interval setting, but it only invalidates when the underlying artifacts change. Trace link changes don’t always trigger cache invalidation because they’re stored separately from artifact metadata. You need to enable ‘Trace Link Change Monitoring’ in the widget advanced settings to force cache refresh when links are added or modified.
That’s helpful context. I checked the service account permissions and it only has READ on requirements and test cases, not on the trace link artifacts themselves. How do I grant permissions to the link artifacts? They don’t appear in the normal artifact permission UI.
Trace link artifacts inherit permissions from their source artifacts by default, but dashboards use a different permission model. You need to grant the dashboard service account the ‘Traceability Reader’ role at the project area level. This role specifically provides READ access to link artifacts across all artifact types in the project. Navigate to Project Area > Permissions > Service Accounts and add your dashboard service account to the Traceability Reader role.