Cannot see back links in ELM Application
After creating a Collaboration Link in Jira, and navigating to the target IBM Engineering Lifecycle Management artifact, there is no back link visible to Jira.
Collaboration Link is created to a IBM Engineering Lifecycle Management application with Configuration Management enabled and a Global Configuration is being used.
- Refresh the page after a minute of having created the Collaboration Link.
Back links are not stored along with the IBM Engineering Lifecycle Management artifact
when a GC is involved, they are managed by IBM Link Index Provider (LDX) and it may take a bit of time for it to be updated.
- Ask to the IBM Link Index Provider (LDX) administrator to verify whether the
OSLC Connect for Jira CM Resources (TRS 2.0) data source is still operative.
- If above data source is still operative and no links are yet reported, ask the Jira administrator to rebuild the
OSLC Connect for Jira CM Resources (TRS 2.0) TRS feed and ask the LQE administrator to re-index this datasource.
- If the application is IBM Engineering Requirements Management DOORS Next or IBM Engineering Test Management,
you may not see the back link because you are not yet authenticated in Jira from this application perspective.
To force the authentication to Jira, initiate the link creation from an application artifact to a Jira issue by opening the selection dialog (for any Collaboration Link type).
Once authenticated (i.e. once Jira issues are visible in the dialog), abort the link creation by closing the selection dialog and refresh the requirement page.
Back links should be visible at this stage.