Enable Auto Save Functionality
It appears there is no auto save functionality. This causes lost work when forgetting to click save at the end of a work day, for example, and your session times out. There are instances where you accidently 'X' out of all tabs and lose work also. Can we have the option to opt into auto save or have a way to recover unsaved data? That would be extremely helpful!Clone Functionality Improvements
When you clone a test case, sometimes you want to keep the links and other times you do not and it can really be a big pain point to remove them all. Jira functionality has a popup that allows you to change the name immediately and asks whether you want to clone attachments or links before creating the clone. Solution: Could Zephyr have a similar popup to allow you to change the name and select whether or not to keep the links attached to the clone before creation?Test Execution - Create Subtask
When I'm executing my test cycle from the the test player and I run into a defect, I need to create a WIP defect. Upon clicking the gear icon and then selecting create subtask, Zephyr brings me to a search parent issue popup. Why doesn't that default to the parent issue that is linked to the test cycle? So many extra clicks and it would save a lot of time for people who test several test cycles on a given day or week. Additionally, when you click next and get the create subtask popup, it typically defaults to subtask or release, which 9 out of 10 times, it will always be a WIP defect that needs creation when testing is in flight. Solution: default parent issue to the one linked in traceability and default create subtask issue type to WIP defect.Ability to reorder test cases within test planning
As a tester, When creating a 'free form' test phase, I would like the option to rearrange my test cases in a specific order for testing. When planning a free-from phase, selecting "maintain hierarchy" only maintains the folder structure; the test cases are placed in a random order after being added.
Add function for testcase version bulk update
Please add the possibility to bulk update TC's to the latest version. Let say if I change a bunch of TC's (e.g. a new custom field was added) and it is necessary to use the latest version in my release, then it is really annoying to update the TC's one by one. Thanks. Regards Matthias
Integration with VersionOne
TestRail is another competitor of Zephyr and allows for easy integration of the Requirements+Defect management tool called “Version One” https://support.testrail.com/hc/en-us/articles/7691128664980-Integrate-with-VersionOne Somos (has procured Zephyr Enterprise licenses) uses Version One for Requirements tracking – Jira (already integrated) with your help yesterday. Now need to integrate VersionOne as well. Can you help or point us to an architect who can help us with the integration? https://www6.v1host.com/SomosInc/Account.mvc/LogIn?destination=%2FSomosInc%2FDefault.aspx%3Fmenu%3DMyHomeEnterpriseGettingStartedPage
Extend test execution related information
To support a continuous risk-based test strategy, hereby requesting the following custom fields and possibilities to be added: -Possibility to add Build Number to an individual test case execution. Hence looking at Execution History will list Status history with associated Build Numbers. -Possibility to filter on Build Number -Possibility to sort on Executed On (I e sort on execution date)Dashboard gadget for Cross project reporting for Test Automation
Currently there is no way easily report on an entire project, most gadgets are release based. It would be helpful to be able to make these dashboard gadgets report data for the entire project, to be able to compare automation efforts across entire projects - Test Automation Status - Test Automation DistributionAbility to use tab to move within test steps
As a user, I need an easy and accessible way to navigate the screen while creating or editing a test case. Currently, you cannot use tab to move to the next text box when creating or updating a test case. It is also very difficult to click to the next test step without it creating a second step below the step you're working on.Customized Test Case Execution statuses need an option to turn the Defect button on or off
When creating a custom execution status, I would like the option to trigger the D button to appear, or not to appear The only statuses that do not trigger the D button to appear are "not executed" and "pass" Use case: I'm trying to create an "Approved" status, and I don't want the D button to appear. I could change the system default "pass" to "approved", but then then the custom status for "Pass" would trigger the D button.Ability to 'Search and Map' to improve usability while mapping test cases and Requirement
Currently, when the User Maps the Requirement to Testcase and Testcase to requirement there is no search and map of the entity. So the user has to go to each and every folder and then map the Testcase or requirement on the pop-up to map test cases or map requirements, give the user the ability to either browse through the directory structure or search. External ID:-ZENT-I-125
Request the number of lines per page be set to a specific default value (i.e. 100) and stick
Currently, the default value is 50 lines per web page. If user set to 100, then it will change back to 50. Request that user can set to a specific value (i.e., 100). Then by logging out and in, it will save the setting. This feature will improve user experience. ThanksAzure ADO plugin or integration with Zephyr Enterprise
To support Zephyr Enterprise Continuous Integration with Azure ADO, Azure DevOps. Azure DevOps (ADO) is a cloud service that we can use to build and test our code project automatically. Azure Pipelines is the solution for Azure PaaS deployments.Improve usability and performances in folder views
When you are navigating the folder structure, every time that you expand a folder, Zephyr make a call to load the first level under the selected folder and it redraws the entire tree or at least it changes the position of the list, making very difficult to work with folders. Sometimes the folder is empty and you lost time and focus on what you are doing. Is it possible to improve the usability of those views? The folders tree should not move after that a node is expanded If a folder has not subfolders should not have the expansion triangle at the left (from the beginning because if you try to expand a folder and it's empty the triangle disappears) Make the expansion of the tree structure faster This is not only in requirements or test repository trees but it's the same for every tree in the application. ThanksZQL - Search for unmapped requirements
As a user, I need the ability to search for requirements or test cases that are un-mapped within Zephyr projects and releases. - Add the ability to search both test cases and requirements for mapped or unmapped (true/false) - Make this available to search across projects and rereleasesAbility to reference a test case within another test case
When creating and executing test cases, having the ability to reference a test case within another test case step/detail will save time, effort, and confusion for users. Being able to just reference an existing test case, instead of re-writing it, will increase efficiency as the user creating the test case and the user who are executing the test case (this allows users to either navigate to the reference test case to follow, or skip it because they already have that knowledge/know the steps.Add features to collapse and preview test steps in Test Execution
When working with a test step with a lot of text or images, it creates a really long test case. It would helpful to limit the vertical size, and add an option to click to expand (adding wrapping and truncation). It would also be helpful to be able to click the image within the test step to launch the image preview. currently you have to leave the test step and scroll the bottom of the test case, preview the image, close it, then scroll back up to the test step to update the exeuction status.Need ability to Edit/Map/Delete tests found via Search
When Tests are found via Search, only the function Export is available at the moment. Once at least one of the found tests is selected, other functions should be available as well: Edit, Map, Delete, Clone (single test or in bulk). External ID:- ZENT-I-362Folder copy from test repository is not retaining the testcase order - CTSD-3106
Hi Team, Folder copy from test repository is not retaining the testcase order, Instead reordering based on testcase id. for example in a folder ACB we have 3 testcases with names one(Order 1), Two(Order2) and Three(Order 3). Then I copied the “abc” folder to "def” folder, now the order is changing based on testcase id.Create a test phase directly from repository folder
As a tester, I get a story (requirement\new feature) to test, then: 1. I begin to design the test cases I going to run and build the test tree under the repository. 2. Map the testing to the requirement. 3. Open a test phase under the test cycle for this story. 4. Move to test execution to run the test phase. I want the option to create test phase directly from the repository folder. Furthermore, I usually, during the test execution, think of more scenarios to test, and I need to go the whole process again from 1-4 for the new scenarios. I want the option to run the test case as part of the phase, from the test case in the repository level.Automation: Create separate Test Phases for each execution under the same Test Cycle
Currently, Vortex allows either reusing the same Test Cycle/Test Phase for all executions, or creating a new Test Cycle for each execution. However, as a User, I'd like to have Vortex creating separate Test Phases for each execution so that I can report on how many times the automation has been run. OLD ID :-ZENT-I-247Lock Test Cycles and Phases to disable executions
As a test lead, I need to be able to lock or disable test cycles and phases so testers can no longer execute test cases or update their statuses. Currently, we only have the ability to Hide/Unhide Test Cycles within releases. However, this does not block any further executions from happening, as you can still find the executions via search.Support for parametrization
Need the ability to reuse test case templates through parametrization in order to allow scaling effectively. I.e., having one test case, and then feeding in parameter values to create variations of the test case at run time so that the same test case can be executed repeatedly with different data values. External ID :- ZENT-I-6Need to be able to close releases
Currently the only option is to hide releases. It would be helpful to be able to "close" releases and put them in a read-only like state, to be able to access any test cases and previous execution data. This should also carry over to dashboards and reports, the only way to see data is for "in progress" releases.
JIRA-Zephyr BDD testcase naming consistent with ZE Vortex automation.
Probelm Statement : There is test case name inconsistency between JIRA BDD plugin and ZE Vortex automation. In case if a scenario has 2 Examples table rows, then JIRA BDD plugin will create 2 test cases with identical test names, e.g. "scenario" and "scenario". While in case if test cases are being created through Vortex for the same type of scenario, they will have different names, e.g. "scenario" and "scenario 2". For Cucumber 7 which we are using right now in our framework, here is the naming conventions: “Scenario - Example #1.1”, “Scenario - Example #1.2”, etc. Previous version of JIRA BDD Plugin, it was creating test cases for all Examples table rows with the SAME name, which was inconstant with how Cucumber default JUnit report was doing, which was giving some indexing to each test case name. Due to this , when we are executing BDD testcase created (containing exdample tables) from JIRA using zephyr, results being attched to same testcase . Current and expected testcase naming snapshots are attched Reference :Case #00535844: Test Case name inconsistencies between JIRA BDD Plugin and Vortex automationTest Repo and Execution Export data - Add the option to remove exporting test steps
For large exports, I would like the option to not export the test steps when pulling data from the Test Repository or Test Execution exports Use case - I need to run a regular report on how many test cases are automated or manual across my project test repository. However with the test steps also being exporting, I have to clean up around 5k of lines each time. **The current dashboard gadget only reports on manual vs automated on the release level. There's no easy way to pull this data for your Project or Global repositoriesAdd the ability to report on test case custom fields
It would be helpful to be able to report on custom field data added to test cases, either in a gadget or through test case export. use case - I have a custom field enabled to select whether a test case is "front-end or back-end." I would like the ability to report on how many test cases have been marked with this custom fieldManage predefine tags list
As administrator, I've noticed that each tester create his own tags and than I have lots of double tags, f.e. Sanity and sanity, Regression and regression etc. I want to have the ability to control it by managing a predefine tags list, thus the tester can only select from this closed list. Also it could be nice if I can delete such tags I don't want to use.Control over new version and un-do/re-do of changes made
When editing a test case, I don't always want a new version created. It would be nice to have a way to un-do or re-do changes before committing a new version to the repository. (it would be helpful to be able to un-do an action such as making changes to or deleting a test step)
Zephyr Enterprise Feature Requests
226 Posts
