Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Current »

In order to create a defect in JIRA, you can look at the results of execution for an automated test case or results of a manual test case execution, and decide that a failure in an execution of a test case is a defect. Each line of these results should now have the iconnext to it. This will allow you to create a defect on each resulting row. Clicking on the above icon to create a defect will launch the following screen. Select JIRA for the drop-down displayed:

Then click on Select link:

At this point, select your project related to the defect found as well as issue type as shown above. After selecting the issue type, the following form will be available for completion. This should have all of the required fields in your JIRA ticketing system in which Summary is populated based on the name of the test case automatically.

Complete the form above and click on Create. This will create a bug ticket in JIRA with the information supplied in the above form. It will also attach the test case steps to the JIRA ticket created. Further, it will make the JIRA ticket available as a link in Subject7. Notice the functions of the buttons below:

Tip

Updating the ticket through Subject7 will reattach all of the artifacts associated with the updated test case. Please note this is a one-way update from Subject7 to JIRA and so if you end up updating JIRA directly, the two may go out of synchronization. Updating a ticket also updates the name, description and summary in JIRA.

Tip

Copying a test case does not copy its existing association with JIRA

Tip

If a JIRA ticket number is added to the Ref ID of manual or automated tests and JIRA is configured under Administration -> Ticketing System, “Go to ticket” link which is next to the Ref ID will open up the associated JIRA ticket in a separate tab within JIRA. This helps with linking manual or automated tests to the JIRA stories for traceability (Requirements Traceability Matrix – RTM) purposes
  • No labels