How to enable rich hover on Report Builder for artifacts belonging to a external OSLC application
Hello community, we have an external OSLC application which we have configured properly to create links with DNG, RQM or CCM. This application comes with a TRS implementation which allow us to register it on LQE so we can generate traceability reports on Report Builder. Everything works fine except when we move the mouse over a DNG requirement, for example, (in an RB report page), we can get the rich hover view (you know, the popup window with the most representative properties) of the artifact and this is not true when we do the same for one of our artifacts in the same page. Is there a way (configuration missing) to do it? So far we think this happens because in order to get such view (oslc:Compact), RB should have our application registered as friend, but we just cannot find a way to do it.
One answer
Comments
Hi Davyd, thank you for your response. Yes, we registered this application with JTS and now it's friend (and consumer) of RM, QM and CCM. This application actually exposes the service for the rich hover because when we create a link from RM for example (let's say an "implemented by" link) and we hover it, we can see the small preview of our artifact in a popup window being at RM, the same happens from QM and CCM. So we know this OSLC application is exposing the service for that but Report Builder does not do the same. Why this could be?
Yes, there is an attibute which is already a URL ("Jira Issue" column), check next screenshot (I'm sorry for not pasting it here but I don't have the required 60 points for doing so)
BTW inspecting the DOM of the report page, I can see the RM link has an extra "data-content" attribute with the iframe information embedded on it and that's missing for our link:
Hello Davyd, I've contacted them and this is what they say:
Supporting rich hover is a combination of two services from OSLC perspective/API (once OAuth authentication is completed). In OSLC, each artifact must have a unique URL for accessing/identifing it. To get a rich hover frame of an artifact, the OSLC client must first request the oslc:Compact view of such artifact at the artifact's URL but with the "application/x-oslc-compact+xml" accept header, this will retrieve the oslc:Compact resource corresponding to the artifact which includes, among other things, the frame height and width and the URL for the content. It is up to the OSLC client to open this frame with such parameters and the frame it self is going to request the second service to load the content. In OSLC Connect for Jira, artifact URLs have the form http[s]://host[:port][/jira]/rest/oslc/1.0/cm/issue/XXX where XXX is the issue key you are interested in.
I tried then the REST client and this is what I got: