Finding all versions of an artifact across configurations
You can create a report that finds all versions of an artifact for IBM® Engineering Test Management or IBM Engineering Requirements Management DOORS® Next projects that are configuration-enabled.
About this task
To create this kind of report, you must know the type of resource that you want to find and its unique ID.
Go to https://server_name:port/rs. On the Reports page, click Build report. If the page doesn't open, contact your application administrator.
Choose a report type.
- Click the pencil icon to select the Lifecycle Query Engine data source (not the Lifecycle Query Engine scoped by a configuration data source).
- Select Current Data (table or graph) to report on the information about artifacts in and across projects.
When you are using the LQE data source, projects that are enabled for
configuration management are hidden by default. In the Limit the scope
section, select the List all project areas when reporting on configurations
themselves checkbox to see configuration-enabled projects in the list.
Choose the projects to report on, and click Continue. If you do not select any projects, the report includes all projects that you can access.
- In the Choose an artifact section, select the Configuration type if you want to find both streams and baselines that contain the artifact. If you want just streams, expand the Configuration twistie and select the Stream type.
In the Trace relationships and add artifacts section:
- Select the Enable multiple paths or add other source artifacts checkbox.
- Click Add a relationship and select the relationship, and click OK.
- From Version Resource, add another relationship that is called Is Version of and choose the type of the artifact that you want to find all versions of. For example, QM Test Plan.
- Under the Selections relationship, click Add a relationship, choose Merge, and click OK. This merge creates a second traceability path by using the existing configuration type.
From this second configuration type, create a Component relationship to
the associated component resource.
Note: You cannot refine the results of a report by specifying a Global Configuration (GC) component anywhere along the tree in the report. The local components do not reference the GC component due to the composition hierarchy through configurations.For example, consider a Global Configuration of 'car 1.0' that consists of two other Global Configurations: 'engine 2.7', 'body 2.9'. The 'engine' consists of three other local components: 'spark plug 1.0', 'piston 1.1', and 'air sensor 3.5'. In this case, a report cannot be created that displays all the requirements that belong to the engine component in the 'car 1.0' Global Configuration.
To create a report that shows as many requirements as possible, you have the following options:
- Find a different level of the GC hierarchy that has exactly the components at the appropriate configuration that you want. In this case, you need to run your report against the 'engine 2.7' GC. It is the best case scenario.
- Run your report against 'car 1.0' but introduce filters against the appropriate artifacts for each component of your choice. The report might not be completed especially if there are multiple trace relationships.
Add a filter in the Set conditions section:
- Click Add condition.
- From the list, select the artifact type that is the target of the Is Version Of relationship, for example QM Test Plan.
- Choose the ID attribute for the component, and select the values to return the artifacts you want.
- In the Choose values list, select is for the operator and enter the exact ID of the artifact that you want to find all versions of.
To keep the window open for adding other conditions, click Add.
Otherwise, click Add and Close.
If you want to trace multiple artifacts of the same type, you can add multiple conditions. If you do not add any conditions, the report extracts all versions of all artifacts of the same type.
Format the results:
- In the Add columns section, click Attribute .
Select the target artifact type (for example QM test plan), choose the
Project Area attribute, and click Add.
- Click the Project Area (QM Test Plan) attribute and drag the attribute to the start of the list.
- Delete the Component 1 ID and URL (Component) 1 columns because you only need the component title.
- Move the Component 1 title column immediately below the Project Area (QM Test Plan) column.
- Delete the Configuration ID column but leave the title and URL columns for the configuration.
- Delete the URL (Version Resource) column as this URL is not useful for most users.
- If you want to distinguish between streams and baselines, add the Mutable attribute for the configuration type and move it below the URL (Configuration) column. You might want to rename the Mutable column to something more meaningful like Is Stream.
Sort the columns into the following order:
- Project Area (QM Test Plan) - ascending
- Component 1 - ascending
- Mutable - descending
- Configuration - ascending
Do not add any other columns from your target artifact type (for example, QM Test Plan) because if the various versions of that artifact have different values for a property, then the SPARQL query execution creates all combinations of the property values for that artifact. Many of the property combinations are invalid.
Run the report.
In the results table, the same artifact title, 'User Acceptance' is listed for each configuration under the QM Test Plan column, where that title is a hyperlink. If you hover over each instance of that artifact, you see the compact rendering of the artifact for the corresponding configuration. In this example, the User Acceptance test plan was modified in component 1 of the project and multiple baselines and streams were created. In addition, that test plan was copied into the initial stream of component 2.
When you are satisfied with the report, click the Name and Share page
title, and specify the details for your report. Click Save.
For more information, see the section Name and share the report in this topic.
What to do next
- To see your report in the list of other reports, click All Reports or My Reports.
- To view a full-page version of your report in a new window, click Open in a new window.
- To further edit your report, click a pencil in the My Choices pane at the right. Click Save to save your changes.
- You can export your report to various document types (Microsoft Word or Excel, PDF, or HTML). To do further editing on the report, export it to IBM Engineering Lifecycle Optimization - Publishing if you have a license. You can also export a report graph to an image file. See the related topics.