Menu

Jira Defects in Portfolio Reporting

Overview

Portfolio Reporting allows for a streamlined approach to viewing and interacting with Jira Defects through the following features:

  • Mapping Jira Defect Severity Values
  • Jira Defect Custom Fields
  • Jira Defect Status Mapping

Mapping Jira Defect Severity Values

This feature allows you to translate defect severity values defined in Jira to a set of standard severity values in Insights. This allows for an easy standardization of defect severity values across all Jira projects integrated with qTest. 

This feature is useful for teams who:

  • work with multiple Jira projects simultaneously,
  • and each Jira project may have different defect severity values (names).

Often, these values will be different in name, but very similar in actual severity. This can happen when Jira projects are defined across an organization (or even subsections of an organization), with multiple projects, and standardization was not implemented.

Example: Your Portfolio has 4 projects and their highest level of severity values are all different names, yet, in reality, they mean the same thing.

  • Project 1=severity value of 'Highest'
  • Project 2=severity value of 'High (P2)'
  • Project 3=severity value of 'Major'
  • Project 4=severity value of 'Test Priority 7'

Therefore, you want to map these differing values to one defect severity value in Insights, such as 'Highest priority,' so you can easily view these defects in one column on the Portfolio Overview table.
Mapping_Severity_Values.png

Where will I see the Jira severity mapping?

You will see the benefit of the Jira severity mapping when you view the Portfolio Overview section of the Report Gallery. 

Before you map your defect severity values, the Portfolio Overview table shows the number of defects that fall within your Jira-defined defect severity values. If a portfolio includes many projects, each with many different severity values, tracking this information becomes difficult, as it displays the number of defects falling within each severity value.

In the example above, before defect severity mapping, the table would show the number of defects that have severity values of 'High,' 'L1,' 'Important,' and 'Show Stopper' in separate columns although they are 'in reality' synonymous. After mapping, the table would only show these defects as falling under the new standard value of 'High.' 
defect_mapping_overview_table.png

To use this feature:

  1. From Insights, select the Settings tab.
  2. In the drop-down menu, select Jira Defect Severity Mapping.
  3. The 'Jira Defect Severity Mapping for Portfolio' page displays.
    Select_Defect_Severity_Mapping_Setting.png 

Add a New Defect Severity Mapping

  1. Select Add, and the 'Projects for Defect Severity Mapping' dialog loads.
  2. Use drag and drop to move your Jira integrated qTest project(s) from the 'Available Projects' field into the 'Selected Projects' field so that you can map defect severity for the selected project(s). Select OK.
  3. The "Jira Severity Field" dialog displays. Here, select the field name associated with tracking severity values in your Jira instance.
    IMPORTANT: The values you see in the Field Name drop-down menu are populating from your Jira project(s) associated with the selected qTest Project(s). The field most commonly used is "Priority." However, if your team has made a custom field to track defect severity in Jira, choose that value from the drop-down menu.
    severity_mapping_added_field_name.png
  4. Select Add, and the 'Defect Severity Mapping Entry' dialog opens.
  5. Enter and assign the following:
    • Insights Severity Name: the standardized severity name that you want to display in Insights
    • Jira Severity Values: your pre-defined Jira Severity Values which are pulling from your Jira instance
      Values.png
      Note: ONLY values that have been assigned to a defect in Jira will populate in Insights. Insights will not pull a defect severity value that has not yet been assigned in Jira because it will not require mapping if it is not being used. You will see standard Jira fields along with your custom Jira fields that are associated with a 'Priority field name.'
  6. Select Update, and the defect severity mapping entries save. Your combined selections display in the 'Defect Severity Mapping' table. 
  7. Continue the Add process until you have mapped all of the desired Jira severity values to a standard Insights severity value. The Add button will disable once all of the Jira severity values are assigned.
  8. Once you have entered all of your severity mappings, select Update again in the 'Defect Severity Mapping' dialog. 

Hint: To better prioritize your defects, try defining severity values on a graded scale. For example, a defect that might not present a significant issue could have a severity value of "Moderate" while a much more serious defect might have a severity value of "Critical."

All_values_mapped.png

Example Use Case

In this Jira project (we will call it Project A) the user had defined custom defect severities using the values "None," "Cosmetic," "Minor," "Average," "Major," and "Fatal." Consider that there is a project in qTest integrated with this Jira instance so that these defect severity values now show in qTest Insights as well.
Screen_Shot_2018-09-25_at_4.25.38_PM.png
Perhaps the user also has a Jira project, project B, in which the Defect severities are defined as values "Not important," "Of little importance," "Approaching important," "Important," "Very important," and "Fix immediately." Like Project A, there is a project in qTest integrated with this Jira instance. While the actual levels of severity might be the same as in project A, the defined values (names given to severity levels) differ. This could be the case between ten different Jira projects, with each having different values for similar grades of severity. 

To simplify defect analysis and reporting, qTest Insight allows the user to map all of these different values in Jira projects A and B onto a standard set of severity values in the Portfolio Report. With this feature, teams can potentially standardize dozens of differing severity values into one set of streamlined values, cleaning up both qTest and Jira environments.

For example, the user could map the severity values "Cosmetic" and "Of little importance" onto an Insights severity value of "Low priority." Upon doing so, the defect severity value of both defects would show up in the Portfolio Report as having a severity value of "Low priority." These new values would show up in the Portfolio Overview section of the Report Gallery.

Edit Existing Defect Severity Values

  1. To edit a mapping, select the 'pencil' icon in the Action column under the "Action" section in the 'JIRA Defect Severity Mapping for Portfolio' table. Choose the pencil icon that corresponds with the severity level value that you want to change.
  2. The 'Defect Severity Mapping' dialog opens. Select the corresponding 'pencil' (edit) or 'X' (delete) icon in the Action column. 
    • If editing, input the new Insights severity name in the corresponding text field and then select the checkbox next to the JIRA severity values that you want to change. Select Update.

Jira Defect Custom Fields

This new feature allows you to select your custom Jira defect fields that you want to see in the Portfolio Details table of the Portfolio Overview report.

To use this feature:

  1. From Insights, select the Settings tab.
  2. In the drop-down menu, select Jira Defect Custom Fields. 
  3. The 'Jira Defect Custom Fields for Portfolio Report' page displays.
  4. Use drag and drop to move your custom Jira field(s)from the 'Available Jira Fields' section into the 'Selected Jira Fields' section. Select OK.
  5. Once you add a custom Jira field to the 'Selected' section, you have the opportunity to edit the column header name that will display in the 'Portfolio Details' table.
    • You can also edit the column Type. Select the 'pencil' icon in the Action column to open the Jira Defect Field dialog.

jira_defect_custom_fields_mapping.png

Once finished, your new Defect custom fields populate in the "Portfolio Details" table in the Portfolio Overview section of Report Gallery.
image__2_.png

Jira Defect Status Mapping

You will need to map Jira Status Values across your qTest Projects, with a standard Insights Status Value. This mapping allows you to view cross-project defect roll-ups, at the portfolio level, within Insights Portfolio Report. Like the Defect Severity Mapping, you can assign multiple Jira Status Values to one Insights Status Value. Also, like Defect Severity Mapping, this feature allows testers to standardize potentially mass amounts of different values into one simple set of values. This allows for a much more streamlined testing environment.

The Insights Chart Color you select here will link the Insights Status Value to a chart color across all projects using Portfolio Reporting. The chart color is not limited to only one status, but you cannot have one status assigned to multiple colors.  

Example: The Insights Status Values of Closed and Fixed are both assigned the same Insights Chart Color pink. Therefore, all Closed and Fixed statuses will be assigned a chart color of pink across all Portfolio Charts. 

color_chart.png

To use this feature, do the following:

  1. From Insights, select the Settings tab.
  2. Select the Jira Defect Status Mapping option, and the page will load.
  3. The Defect status Mapping will display in the table.

Add a New Defect Status Mapping

  1. Select Add and the "Projects for Defect Status Mapping" dialog loads.
  2. Locate the desired project(s) from the Available Projects column and use drag/drop to move it to the Selected Projects column.
    project_mapping_defect_status.png
  3. Select OK, and the Defect Status Mapping dialog will populate with the new qTest Projects you selected.
  4.  Select the Add button to map the Insights Status Value with the Jira Status Value. 
    add_values.png
  5. The "Defect Status Mapping Entry" dialog opens, and you will enter or assign the following:
    • Insights Status Value-the standard name that will display in Insights
    • Jira Status Value-your Jira Status Values
      add_status_value.png
  6. Select Update and the Defect Status mapping entries will save. Your combined selections will display in the Defect Status mapping table. 
    values_added.png
  7. Once you have entered all of your status mappings, select Update in the "Defect Status Mapping" dialog and the Projects with their assigned values and mappings will display in the Jira Defect Status Mapping for Portfolio table.
    defect_status_mapping_page.png

Edit Existing Defect Status Mappings

  1. From Insights, select the Settings tab.
  2. Select the Jira Status Mapping option and the page loads.
  3. Locate the qTest Projects you would like to edit and select the pencil icon in the Action column. 
  4. The Defect Status Mapping dialog will open, and you can edit the Projects by selecting the Update Projects button.
    update_projects_defect_status_mapping.png
  5. The Defect Status Mapping dialog opens, and you can use drag/drop to edit the Selected Project column by either adding additional projects or removing existing ones.
  6. Select Ok, and the Project Mapping will update on the Default Status Mapping dialog.
  7. Select Update and the Jira Defect Status Mapping for Portfolio page will load with your new changes. 

Assign an Insights Color Value

  1. On the Jira Defect Status Mapping for Portfolio page, select the chart color in the Insights Chart Color column.
  2. The Insights Chart Color dialog opens, and you can enter the varchar Chart Color, or select the color tile and visually choose the desired color. Save.
    insights_chart_color_dialog.png

 

 

Powered by Zendesk