It's all about the answers!

Ask a question

Artifact Type value in JRS report


Miroslav Zaninovic (36723) | asked Sep 25 '20, 10:09 a.m.
Hi,
When we create JRS report in report builder, data source is LQE, can we somehow get artifact type as artifact attribute value?
Currently artifact types are visible next to each attribute name in the name row, and type attributes shows values requirement or text.

Tnx

Accepted answer


permanent link
Kathryn Fryer (461) | answered Nov 24 '20, 6:08 p.m.

What ELM version are you using? In 701, I was able to select the generic "Requirement" as the artifact, and add the "Type" attribute as a column in Format Results, which then shows the specific requirement type (System Requirement, Heading, etc) in the results. The behaviour might have been different in previous releases.

Miroslav Zaninovic selected this answer as the correct answer

Comments
Miroslav Zaninovic commented Nov 25 '20, 5:47 a.m.
thank you!
If you select specific artifact type in traceability relations then you do not have clear types. it is on 7.0.1

One other answer



permanent link
Kathryn Fryer (461) | answered Nov 25 '20, 11:05 a.m.
If your trace path is to a specific type of requirement, the name of that type is shown in the column header, so I'm not sure why you'd want an additional column for the type as well.
Alternatively, you could trace to a generic "requirement", and use a condition to scope that 2nd requirement to the type(s) you want using the Type attribute, which you could then display in the table. If you have complex traceability paths and other conditional processing, you'd want to test that for performance.
Hope that helps.

Comments
Miroslav Zaninovic commented Nov 30 '20, 5:18 a.m.

My idea is to export JRS report as XLS, and then be able to use it for XLS exchange in DNG. Export module from JRS and import it as xls.


Kathryn Fryer commented Nov 30 '20, 9:03 a.m.
Do you mean to recreate the same data in another DNG instance or project area? That's an interesting idea. Have you looked at ReqIF to do the export/import? You can define views that determine the artifacts and data to exchange.

The challenge in the JRS export is including all the type information that you need, including URIs, correct labels, link direction (LQE does some "magic" to ensure links can be traced in both directions). In addition to the type question you raised, the link types are also not exposed in the results. So if you chose to go this route, you'd need to do some amount of post-processing.


Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.