Engineering Test Manager (aka QM) provides the ability to track quality tasks. These tasks are intended to manage the development task that are being performed in developing test artifacts.
Setting up the Usage of Quality Tasks
To enable the usage of these quality tasks we need to add the project associations of our tools.
In ETM, our project must create an association to our Jira project where we want to store our Jira Quality Tasks. So in the Project Administration add the Uses - Quality Management Tasks relationship.
In Jira, we want to provide the inverse relationship, Provides - Quality Management Tasks.
This will provide access to the following OSLC relationships.
From here we can leverage the relationships in our linking between our projects.
Linking from Jira
Linking from Jira will provide the standard OSLC Experience from a Change Provider. When your Jira project association Provides - Quality Management Tasks the option to create Related Test Artifacts is enabled. For example, creating a Related Test Case relationship from a Jira Task.
When we link to an existing artifact we get the standard ETM dialog.
And results in a link in Jira.
And then a backlink in ETM.
The standard relationship that is seen in QM is that of a “Related Change Request”. As well the more detail linking to a specific section of the test artifact is not done from the Jira side on linking.
If you are using Global Configuration, this link may not be visible immediately in QM and could take a minute or two to be discovered by ETM. This is normal behavior by ETM.
This behavior is the same for all other Related test artifacts.
Linking from ETM
Linking from ETM provides a more detailed integration for those tracking specific activities on the test artifacts.
The Quality Task icons indicate a specific opportunity to link to a more detailed part of the Test Artifact. These options are available whenever these icons are shown.
The option is available to link to an existing element or create a new one. When initiation of the create option, some of the fields will be automatically populated including the summary and description and the normal Jira form is available for you to add more detail.
Once you create the artifact your link will be available. And make sure you save the ETM artifact to finalize the link with Jira (different behavior from the Change Tool that makes the link immediately).
When you make these links from ETM, you will have both references on the specific section as the quality task as well as the Related Change Request (which is the primary OSLC relationship)
Notes on Deleting Relationships
We have noted from both EWM and Jira customers some question on the behavior of delete of the link. The standard behavior of QM with all change tools is the same.
Delete from Jira (or EWM)
When you delete from within your change tool it will delete the OSLC relationship and will be acknowledged by ETM that the relationship has been deleted. However, it will not delete the interior quality task relationship within the test artifact section. This link is not an issue, but awareness should be understood.
This would look like the following if the link was deleted from Jira for AMR70-78 from within Jira even though a precise quality task has been referenced.
Delete from ETM
When you delete from ETM, there is a slightly different relationship. ETM will perform the delete from the Quality Task relationship and will delete both the Quality Task as well as the Related Change Request relationship.
After the delete, there is a clean removal on both the Quality Task and the Related Change Request.
The update may take several minutes on the Related Change Requests as the index updates, but it has been removed. You can verify this by looking at the rich hover on the deleted referenced item and it will no longer show the link to the ETM item.
Special Case (Rare)
There is one special case of note. When you have used the same Change ticket on the same ETM artifact in several sections (of the same artifact), if you perform a delete in one Quality Task section it will delete the relationship back from Jira even if other QT relationships exist. ETM does not check this before it requests the link deletion.
Based on these behaviors we have some simple recommended practices to have behaviors you want to have.
Create and Delete Links from the same side of the relationship. A common practice of doing this will prevent dangling QT relationship that may seem strange for your users.
If you use Quality Tasks on an artifact, use unique tasks for each section. This will prevent the deletion of the backlink in Jira if you remove a single quality task link to the same artifact.
If you follow those simple rules you will have success in using and reporting on your ETM links.
Extended Configurations of Note
In OSLC Connect for Jira, we do have options to maximize your experience with ETM and your desired workflow. The following features can help customize your experience.
Select your Quality Task Default Type
In the Jira Admin console, you can configure the Quality Task type for your Jira Scheme.
This allows you to leverage your custom configuration and make sure teams are using the desired types for quality tasks.
Select your Preview for your Quality Task
If you want to view specific contents of your Quality Tasks from ETM, customize the rich preview from Jira.
You are able to use Jira View Screen Schemes to adjust the contents on your preview.
Control what Artifacts are linked from Jira
We know that there are process controls on what artifact links you want to enable users to create. We enable the selection of what are allowable link dialogs based on your Jira Issue Type.
For example, maybe there is only a few of the Quality relationship your team wants for a type, you can restrict them being presented as options.
As well you can set a default link relationship for a type.
Control the Field Mappings for GC
In your project you control the version mappings for a field. When using Quality Task you may need to review for consistency.
For example when using Quality Tasks, Fix Version is a standard versioning of relationship as the Related Change Request is looking at the “current” version for the work.