QMetry
QMetry Test Management for Jira (QTM4J) is a test management solution developed by SmartBear.
Data import from QMetry is available on eazyBI for Jira Cloud.
This integration is available in beta testing. Please reach out to eazyBI Support if you would like to get early access and start using it now.
On this page:
Data Import
If you have installed the QMetry app, you will see the QMetry option in the Jira import options.
You should authorize data import for QMetry on Cloud. Please specify the QMetry API key to import QMetry data.
Go to Jira → QMetry Configuration → Open API and generate the API key. Copy the key and paste it in the eazyBI import options field QMetry API key.
Limit imported test executions
To reduce import time and the testing data in the cube, you can import only the most recent test case executions. This will reduce both import time and report performance.
You can set a relative limit for an individual account. In the import options, add the period in the field "Imported Test Execution limit". Set a relative time limit for test executions, like 3 months importing test executions from the last three months, or a particular date, like Jun 14 2025 setting a date range from that date until now. Test executions are imported if they are created (test case is added to the cycle) within the time limit (for scheduled test executions) or the actual start date is within the time limit (for executed or in progress test executions). If no limit is set, all test executions are imported.
Another option is to set the limit for all accounts (the entire eazyBI instance) through the eazyBI site settings. If import limits are applied to the entire eazyBI instance using advanced settings, then the limit in import options (individually set for the account) won't exceed the limit in advanced settings. In such a way, the overall limits can be set on the eazyBI account, and, in an individual account, this time can be reduced further.
[jira.qmetry] test_executions_limit = "3 months"
Dimensions
After the import, the following QMetry-specific dimensions are created:
QMetry Defect | Defect issues added during the testing. The dimension is organized in Project and Defect levels. In addition, you can add add Issue hierarchy to group defect issues. |
|---|---|
QMetry Environment | Environments of test execution. |
QMetry Test Case | Created test cases. The dimension is organized by Project and Test Case. You can add custom hierarchy based on Test Case properties. |
QMetry Test Case Assignee | User assigned to a test cases. |
QMetry Test Case Component | Components assigned to a tests case. If several components are entered for a test case then it is counted for each component. |
QMetry Test Case Fix Version | Fix Versions assigned to a tests case. The dimension is organised by Project, Status, and Test Case Fix Version. This dimension has additional hiearachies, By name and By status, to group version by other criteria across all projects. If several fix versions are entered for a test case then it is counted for each version. |
QMetry Test Case Folder | Folder name in which Test Case is added. The dimension is organized by default hierarchy or by folder hierarchy (in Parent Folder and Test Case Folder). |
QMetry Test Case Label | Labels assigned to a tests case. If several labels are entered for a test case then it is counted for each label. |
QMetry Test Case Priority | Priority assigned to a tests case. |
QMetry Test Case Reporter | Reporter of a tests case. |
QMetry Test Case Sprint | Sprint assigned to a tests case. |
QMetry Test Case Status | Status assigned to a tests case. |
QMetry Test Case Story | Directly linked stories to a test case. The dimension is organized in Project and Test Case Story levels. In addition, you can add add Issue hierarchy to group requirement issues. |
QMetry Test Case Type | Type of a test case (Manual, Automated). |
QMetry Test Cycle | Created test cycles. The dimension is organized by default hierarchy (in Project and Test Cycle levels) or by folder hierarchy (in Project, Folder, Subfolder and Test Cycle). You can add custom hierarchy based on Test Case properties. |
QMetry Test Cycle Assignee | User currently assigned to a test cycle. |
QMetry Test Cycle Component | Component assigned to a test cycle. If several components are entered for a test case then it is counted for each component. |
QMetry Test Cycle Fix Version | Fix version assigned to a test cycle. The dimension is organised by Project, Status, and Test Cycle Fix Version. This dimension has additional hiearachies, By name and By status, to group version by other criteria across all projects. If several fix versions are entered for a test case then it is counted for each version. |
QMetry Test Cycle Label | Label assigned of a test cycle. If several labels are entered for a test case then it is counted for each label. |
QMetry Test Cycle Priority | Priority currently assigned to a test cycle. |
QMetry Test Cycle Reporter | Reporter assigned to a test cycle. |
QMetry Test Cycle Sprint | Sprint assigned to a test cycle |
QMetry Test Cycle Status | Current status of a test cycle. |
QMetry Test Cycle Story | Directly linked stories to a test cycle. The dimension is organized in Project and Test Cycle Story levels. In addition, you can add add Issue hierarchy to group requirement issues. |
QMetry Test Execution | All tests executions; one execution is a combination of one test case and one test cycle to which it is added. The dimension is organized by default hierarchy (in Project and Test Execution levels) or by Test Case hierarchy (in Project, Test Case, and Test Execution). Execution member names consist of Test Case key, Test Cycle key, unique ID (the same as in QMetry) and a Test Case summary. |
QMetry Test Executed by | Users who performed a test execution. |
QMetry Test Execution Assignee | User who is assigned to a test execution. |
QMetry Test Execution Result | Latest execution result of test execution (Pass, Fail, Work In Progress, Not Executed, Blocked, etc.) |
QMetry Test Plan | Created test plans. The dimension is organized by default hierarchy (in Project and Test Plan levels) or by folder hierarchy (in Project, Folder, Subfolder and Test Plan). You can add custom hierarchy based on Test Case properties. |
Measures
The following QMetry-specific measures can be analyzed by QMetry-specific dimensions and by a few standard dimensions, Time and Project. The rest of the standard dimensions, such as Fix Version or Assignee, are not compatible with QMetr-specific measures; use specialized dimensions like QMetry Test Case Fix Version or QMetry Test Cycle Assignee instead.
You can interact with report and see a list of test cases, test cycles and executions behind the value. In the report, click on the cell value or chart item to Drill through test cycles for a detailed list of executions, including additional details on the execution date, the user who executed it, the result, and the comments. Or you can Drill through → Test Case or Test Cycle to get a list of relevant Test or Test Execution issues with an active hyperlink to Jira issues.
QMetry Test Cases created | How many test cases are created. On the Time dimension, data are grouped by the test case creation date. This measure works with dimensions representing test cases, like QMetry Test Case Status. If you need to see how many tests cases are associated with each test cycle, execution or test plan use another measure QMetry Test Cases with Test Cycles. |
|---|---|
QMetry Actual Test Cases | How many created test cases are still actual within the selected dimensions. |
QMetry Test Cycles created | How many test cycles are created. On the Time dimension, data are grouped by the test cycle creation date. This measure works with dimensions representing test cycles and test plan, like QMetry Test Cycle Status and Qmetry Test Plan. |
QMetry Execution time | How much time in minutes took to execute test cases. On the Time dimension, data are grouped by the execution date. |
QMetry Test Cases executed | How many test cases are executed within selected dimensions; test executions are not in "Not Executed" or "Work In Progress" statuses. On the Time dimension, data are grouped by the execution date. |
QMetry Test Cases executing | How many test cases are currently executed (in progress) within selected dimensions; test executions are in "Work In Progress" status. On the Time dimension, data are grouped by the execution date. |
QMetry Test Cases scheduled | How many test cases are scheduled within selected dimensions but not yet executed; test executions are in "Not Executed" status. On the Time dimension, data are grouped by the execution creation–date when test case was added to the test cycle. |
QMetry Test Case defects | How many defects are registered for test executions. On the Time dimension, data are grouped by the execution date. A unique count of different defects is returned for each row in a report. |
QMetry Executions | How many times test cases have been executed, are executing or scheduled for execution. On the Time dimension, data are grouped by the execution date for completed and in progress executions or execution creation date for scheduled executions. |
QMetry Test Cases with Test Cycles | How many test cases have at least one test cycle scheduled, in progress or completed. On the Time dimension, data are grouped by the execution date for completed and in progress executions or execution creation date for scheduled executions |
QMetry Execution first date | Date when a test case is executed for the first time in a report context. |
QMetry Execution last date | Date when a test case is executed for the last time in a report context. |
QMetry Average execution time | Average execution time in minutes per completed executions. Average is calculated of measure QMetry Execution time divide by QMetry Executions in a report context. |
QMetry Estimated execution time | Estimated execution time in minutes in a report context. |
QMetry Execution summary | List of execution results separated by a comma and how many QMetry Executions are for each execution result. |
Properties
The following QMetry-specific properties are created.
QMetry Test Case created date | The created date of a test case. This is a test case property and should be used together with QMetry Test Case dimension. |
|---|---|
QMetry Test Case estimated time | Current estimated execution time in minutes of the test case. This is a test case property and should be used together with QMetry Test Case dimension. |
QMetry Test Case reporter | The reporter name of a test case. This is a test case property and should be used together with QMetry Test Case dimension. |
QMetry Test Case archived? | An indication of whether the test case is actual or archived. This is a test case property and should be used together with QMetry Test Case dimension. |
QMetry Test Case type | The type of a test case. This is a test case property and should be used together with QMetry Test Case dimension. |
QMetry Test Case last executed by | The user who did the last execution of a test case. This is a test case property and should be used together with QMetry Test Case dimension. |
QMetry Test Case last execution date | The last execution date of a test case. This is a test case property and should be used together with QMetry Test Case dimension. |
QMetry Test Case last execution result | The last execution result of a test case. This is a test case property and should be used together with QMetry Test Case dimension. |
| QMetry Test Cycle planned start date | Planned start date of the test cycle. This is a test cycle property and should be used together with QMetry Test Cycle dimension. |
| QMetry Test Cycle planned end date | The planned end date of the test cycle. This is a test cycle property and should be used together with QMetry Test Cycle dimension. |
| QMetry Test Cycle reporter | The reporter name of a test case. This is a test case property and should be used together with QMetry Test Cycle dimension. |
| QMetry Test Cycle archived? | An indication of whether the test cycle is actual or archived. This is a test case property and should be used together with QMetry Test Cycle dimension. |
| QMetry Test Plan created date | Registered creation date of the test plan. This is a test plan property and should be used together with QMetry Test Plan dimension. |
| QMetry Test Plan reporter | The reporter name of a test plan. This is a test case property and should be used together with QMetry Test Plan dimension. |
| QMetry Test Plan archived? | An indication of whether the test plan is actual or archived. This is a test case property and should be used together with QMetry Test Plan dimension. |
| QMetry Test Case Story status | Current status of the linked story to a test case. This is a test requirement property and should be used together with QMetry Test Case Story dimension. |
| QMetry Test Case Fix Version start date | The start date of a fix version assigned to a Test Case. This is a test case property and should be used together with QMetry Test Case Fix Version dimension. |
| QMetry Test Case Fix Version release date | The release date of a fix version assigned to a Test Case. This is a test case property and should be used together with QMetry Test Case Fix Version dimension. |
| QMetry Test Cycle Fix Version start date | The start date of a fix version assigned to a Test Cycle. This is a test case property and should be used together with QMetry Test Cycle Fix Version dimension. |
| QMetry Test Cycle Fix Version release date | The release date of a fix version assigned to a Test Cycle. This is a test case property and should be used together with QMetry Test Cycle Fix Version dimension. |
| QMetry Test Case Story status | The current status of a story linked to a Test Case. This is a linked story property and should be used together with QMetry Test Case Story dimension. |
| QMetry Test Cycle Story status | The current status of a story linked to a Test Cycle. This is a linked story property and should be used together with QMetry Test Cycle Story dimension. |
Issue properties
Dimensions Qmetry Defect, QMetry Test Case Story, QMetry Test Cycle Story are Jira issues, which are also represented in the Issue dimension. You can define a calculated measure to get any issue property that is imported in eazyBI, also for those three QMetry specific dimensions.
To access issue property, use function get(). For example, to get priority for QMetry Defect, copy a formula of the issue property Issue Priority and replace the dimension name [Issue] with [QMetry Defect] like this:
[Priority].[Priority].getMemberNameByKey(
[QMetry Defect].CurrentHierarchyMember.get('Priority ID')
)
Another example, to get the resolution date for QMetry Test Case Story, copy a formula of issue property Issue resolution date and replace dimension name [Issue] with [QMetry Test Case Story] like this:
[QMetry Test Case Story].CurrentHierarchyMember.get('Resolved at')
Add Issue hierarchy
You can group issues representing stories or defects by Plans hierarchy or any other hierarchy you have built for the Issue dimension.
Additional hierarchies for QMetry dimensions are defined in eazyBI site settings for Cloud and are marked with the setting [[jira.qmetry.custom_hierarchies]]. Provide the dimension name for which to enable the hierarchy, the hierarchy name, and the top-level member name. List all hierarchy levels where the bottom level is a requirement/defect issue (sub-task level is not supported).
For example, enable Epic hierarchy for the "QMetry Defect" dimension with three hierarchy levels: project of defect issue, Epic related to defect issue, and defect issue.
[[jira.qmetry.custom_hierarchies]]
dimension = "Qmetry Defect"
hierarchy = "Epic"
all_member_name = "All Defects by Epics"
levels = [
{name="Project",key_column = "project_key"},
{name="Epic",key_column="epic_key"},
{name="Defect"}
]
If you already have constructed an additional Issue hierarchy, you can enable it also for QMetry dimensions. Suppose you have a Features by Stories hierarchy as described in this example Separate hierarchy level for Story between parent and epic. Specify the dimension name for which to make the hierarchy, the hierarchy name, and the top-level member name. The levels should match the additional issue hierarchy description except for the Sub-task level and no parameters for the lowest (requirement or defect) level.
[[jira.qmetry.custom_hierarchies]]
dimension = "QMetry Test Case Story"
hierarchy = "Features by Stories"
all_member_name = "All Issues by Features"
levels = [
{name="Feature",key_column="customfield_featuree",issue_type="Feature"},
{name="Epic and risk",key_column="customfield_epice",issue_type="Epic"},
{name="Story",key_column="customfield_storye",issue_type="Story"},
{name="Requirement"},
]
You can enable the Plans hierarchy as well. In that case, list all hierarchy levels and parent keys matching the hierarchy configuration in Jira. The example below describes the Plans hierarchy for Initiative → Epic → Story and enables it to the "QMetry Test Case Story" dimension.
[[jira.qmetry.custom_hierarchies]]
dimension = "QMetry Test Case Story"
hierarchy = "Plans"
all_member_name = "All requirements by Initiatives"
levels = [
{name="Initiative",key_column = "jpoh_parent_3"},
{name="Epic",key_column="jpoh_parent_2"},
{name="Story"}
]
Sample reports
If you selected the Import sample reports option, additional sample reports are created in the Samples QMetry folder. Please try these reports to see which measures would be useful for your specific needs. If you would like to customize some reports, then save them and change the name (as the default sample reports are overwritten during each Jira import).
