Zephyr Essential Test Management for Jira
eazyBI for Jira
Zephyr Essential - Test Management for Jira is a test management tool within Jira developed by SmartBear.
Data import from Zephyr Essential 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.
If you have the legacy version of the app, Zephyr Squad, please see the documentation for Zephyr Squad Test Management for Jira.
On this page:
Data Import
You will see the Zephyr Essential option in Jira import options if you have installed Zephyr Essential - Test Management for Jira. If you do not see this option, please reach out to eazyBI Support to enable this new integartion for you.
You should authorize data import for Zephyr Essential on Cloud using the Access Token. Go to the Zephyr Essential API Access Tokens page by clicking the link below the field, then create a new token and enter it in the eazyBI import options.
Limit imported test executions
To reduce import time and the testing data in the cube, you can import only the most recent test 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 2026 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.zephyr_essential] test_executions_limit = "3 months"
Dimensions
After the import, the following Zephyr Essential specific dimensions are added:
Zephyr Essential Defect | Defect issues were added during the testing through the test player screen. The dimension is organized in Project and Defect levels. You can add add Issue hierarchy to group defect issues. |
|---|---|
Zephyr Essential Environment | Environments of scheduled, in progress, and completed test executions. |
Zephyr Essential Requirement | Requirement issues linked to test cases. The dimension is organized in Project and Requirement levels. In addition, you can add add Issue hierarchy to group requirement issues. |
Zephyr Essential Test Assigned To | Users who are assigned to tests within test cycles. |
Zephyr Essential Test Case | Created test cases. The dimension is organized by default hierarchy (in Project and Test Case levels) or by folder hierarchy (in Project, Folder, Subfolder, and Test Case). In addition, you can add a custom hierarchy based on Test Case properties. |
Zephyr Essential Test Case Label | Current labels of test cases. If several labels are added for a test case, then it is counted for each label. |
Zephyr Essential Test Case Owner | Current owners of test cases. |
Zephyr Essential Test Case Priority | Current priorities of test cases. |
Zephyr Essential Test Case Status | Statuses of test cases. |
Zephyr Essential 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). In addition, you can add a custom hierarchy based on Test Cycle properties. |
Zephyr Essential Test Cycle Owner | Current owners of test cycles. |
Zephyr Essential Test Cycle Related Issue | Jira issues related to test cycles. The dimension is organized in Project and Related Issue levels. |
Zephyr Essential Test Cycle Status | Current statuses of test cycles. |
Zephyr Essential Test Executed by | Users who have executed tests. |
Zephyr Essential Test Plan | Created test plans. The dimension is organized by default hierarchy (in Project and Test Plan levels), by folder hierarchy (in Project, Folder, Subfolder and Test Plan), or by Status (. In addition, you can add a custom hierarchy based on Test Plan properties, for example, Test Plan Status. |
Zephyr Essential Test Result Status | Statuses of test case executions (Passed, Failed, In Progress, Not Executed, etc) |
Zephyr Essential Test Script Type | Types of test scripts: step-by-step or unknown. |
Zephyr Essential Test Execution (hidden) | The hidden dimension of test executions could be used only in calculated measures. Member names are execution IDs. |
Measures
The following Zephyr Essential-specific measures are imported. These measures can be analyzed by the mentioned Zephyr Essential specific dimensions and by a few standard dimensions: Time, Project, Component, Fix Version, and Week Day.
The measures used in the report define the context of standard dimensions and represent the project, component, or version of test cases or test cycles. For example, when using execution-related measures, like Zephyr Essential Execution time, Zephyr Essential Test Cases executed, Zephyr Essential Test Cases with Test Cycles, and others, then the standard dimensions Project and Fix Version represent data on Test Cycle.
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 open the Detailed list of test cycles, which contains executions with additional details on the execution date, the user who executed it, the execution status, and the comment. 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.
Zephyr Essential Test Cases created | How many test cases are created. |
|---|---|
Zephyr Essential Test Cycles created | How many test cycles are created. |
Zephyr Essential Test Cases executed | How many test cases are executed within selected dimensions; test executions are not in "Not Executed" or "In Progress" statuses. |
Zephyr Essential Test Cases executing | How many test cases are currently executed (in progress) within selected dimensions; test executions are in "In Progress" status. |
Zephyr Essential Test Cases scheduled | How many test cases are scheduled within selected dimensions but not yet executed; test executions are in "Not Executed" status. |
Zephyr Essential Test Case defects | How many defects are registered for test executions. A unique count of different defects is returned for each row in a report. |
Zephyr Essential Executions | How many times test cases have been executed, are executing or scheduled for execution. |
Zephyr Essential Automated executions | How many times test cases have been executed, are executing or scheduled for the execution with an automation tool. |
Zephyr Essential Test Cases with Test Cycles | How many test cases have at least one test cycle scheduled, in progress or completed. |
Zephyr Essential Execution first date | Date when a test case is executed for the first time within the selected context (selected environment, time period, test plan, etc.). |
Zephyr Essential Execution last date | Date when a test case is executed for the last time within the selected context (selected environment, time period, test plan, etc.). |
Zephyr Essential Execution time | How much time in minutes took to execute test cases. |
Zephyr Essential Estimated execution time | Estimated execution time in minutes. |
Zephyr Essential Average execution time | Average execution time in minutes per completed executions. Average is calculated as Zephyr Essential Execution time divided by the Zephyr Essential Executions. |
Zephyr Essential Execution summary | List of test result statuses separated by a comma and how many Zephyr Essential Executions are for each test result status. |
Zephyr Essential Actual Test Cases | How many created test cases are still actual (not archived) within the selected dimensions. |
Issues in Fix version | How many Jira issues with or without any testing coverage or relation to test cycles are assigned to the selected Fix version. This measure is based on a predefined measure, Issue created, and should be used together with the dimension Fix Version. |
Properties
The following Zephyr Essential specific properties will be created.
Zephyr Essential Test Case last execution date | Last execution date of the test case. This is a test case property and should be used together with Zephyr Essential Test Case dimension. |
|---|---|
Zephyr Essential Test Case last executed by | The user who did the last execution of the test case. This is a test case property and should be used together with Zephyr Essential Test Case dimension. |
Zephyr Essential 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 Zephyr Essential Test Case dimension. |
Zephyr Essential Test Case last execution status | Last execution status of the test case. This is a test case property and should be used together with Zephyr Essential Test Case dimension. |
Zephyr Essential Test Case last execution version | The version of the last execution of the test case. This is a test case property and should be used together with Zephyr Essential Test Case dimension. |
Zephyr Essential Test Case created date | The date and time when the test case is created. This is a test case property and should be used together with Zephyr Essential Test Case dimension. |
Zephyr Essential Test Case owner | The owner of the test case. This is a test case property and should be used together with Zephyr Essential Test Case dimension. |
Zephyr Essential 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 Zephyr Essential Test Case dimension. |
Zephyr Essential Test Cycle planned start date | Planned start date of the test cycle. This is a test cycle property and should be used together with Zephyr Essential Test Cycles dimension. |
Zephyr Essential 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 Zephyr Essential Test Cycles dimension. |
Zephyr Essential Test Cycle owner | The owner of the test cycle. This is a test cycle property and should be used together with Zephyr Essential Test Cycles dimension. |
Zephyr Essential Test Plan status | Current status of the test plan. This is a test plan property and should be used together with Zephyr Essential Test Plan dimension. |
Zephyr Essential Test Plan labels | The current labels for the test plan. This is a test plan property and should be used together with Zephyr Essential Test Plan dimension. |
Zephyr Essential Test Plan owner | Current owner of the test plan. This is a test plan property and should be used together with Zephyr Essential Test Plan dimension. |
Zephyr Essential Test Plan related issues | Keys of the Issues linked to the test plan. This is a test plan property and should be used together with Zephyr Essential Test Plan dimension. |
Zephyr Essential Requirement status | Current status of the requirement issue. This is a test requirement property and should be used together with Zephyr Essential Requirement dimension. You can create calculated measures to show other issue properties for Zephyr Essential Requirements, like priority, labels, assignee, and others. |
Issue properties
Dimensions Zephyr Essential Defect, Zephyr Essential Requirement, and Zephyr Essential Test Cycle Related Issue are Jira issues that 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 Zephyr Essential-specific dimensions. To access issue property, use function get().
For example, to get priority for Zephyr Essential Defect, copy a formula of the issue property Issue Priority and replace the dimension name [Issue] with [Zephyr Essential Defect] like this:
[Priority].[Priority].getMemberNameByKey(
[Zephyr Essential Defect].CurrentHierarchyMember.get('Priority ID')
)
Another example, to get the resolution date for Zephyr Essential Requirement, copy a formula of the issue property Issue resolution date and replace the dimension name [Issue] with [Zephyr Essential Requirement] like this:
[Zephyr Essential Requirement].CurrentHierarchyMember.get('Resolved at')
Add Issue hierarchy
In the Zephyr Essential Defect and Zephyr Essential Requirement dimensions, you can group issues by the Epic and Plans hierarchies, or by any other hierarchy you have built for the Issue dimension. Note that hierarchy should be represented in the Issue dimension first to make it work for Zephyr Essential dimensions.
Additional hierarchies for Zephyr Essential dimensions are defined in the eazyBI site settings and are marked with the setting [[jira.zephyr_essential.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 Zephyr Essential Defect dimension with three hierarchy levels: project of defect issue, Epic related to defect issue, and defect issue.
[[jira.zephyr_essential.custom_hierarchies]]
dimension = "Zephyr Essential 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"}
]
To enable the Parent hierarchy, list all hierarchy levels and parent keys that match the hierarchy configuration in Jira. List all Parent hierarchy levels where the bottom level is a requirement/defect issue, specify the key column parameter for each level describing its location in the hierarchy, counting from the bottom.
The example below describes the Parent hierarchy for Initiative → Epic → Story and enables it in the Zephyr Essential Requirement dimension.
[[jira.zephyr_essential.custom_hierarchies]]
dimension = "Zephyr Essential Requirement"
hierarchy = "Parent"
all_member_name = "All requirements by Initiatives"
levels = [
{name="Initiative",key_column = "jpoh_parent_3"}, #third level from bottom
{name="Epic",key_column="jpoh_parent_2"}, #second level from bottom
{name="Story"} # this is the first level in parent hierarchy, no need to specify the key column
]
If you have already constructed an additional Issue hierarchy, you can also enable it for Zephyr Essential 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.zephyr_essential.custom_hierarchies]]
dimension = "Zephyr Essential Requirement"
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"},
]
Sample reports
If you selected the Import sample reports option, then additional sample reports are created in the Samples Zephyr Essential 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).
