Enhance formatting and default options for users.
There are several enhancements requested to facilitate user interaction with Zephyr Enterprise: Enhancement # 1: Make all Checkboxes larger. The smaller checkboxes make it difficult for some users to select an option on the first attempt. Export/Report checkboxes Test Case checkboxes Enhancement #2: Make scrollbars wider. The thin scrollbars make it difficult to slide with ease and difficult to see. Enhancement#3: Default options are needed at the user level for sort/font/Filter. a) Sort: An enhancement was requested for alphabetical for folders. The sorting option needs to be defaulted at the user level b) Font: Users should be able to set the default FONT when creating test cases in the testcase repository. Today users have to reselect the font for each entry/cell c) Filter: Users should be able select a default filter (query) as that would enable users to see their information immediately. Enhancement #4: Divider lines are difficult to see on list views from filters. Please make them more prominent. Enhancement #5: User dashboards are needed that would be similar to the release summary for these sections. My Requirements My Test Cases My Test Planning My Test ExecutionsUsers should be able to pre-plan in Jira Sync for requirements
Today if a user tries to input a JQL query for planned stories, Zephyr Enterprise does not enable the save button because 0 results are pulled. The situation where a user would have 0 results could be because stories that meet the criteria have not been created yet in JIRA. The JQL queries are consistent across releases. (A difference could be March vs April in the selection criteria, for example.) The enhancement would allow a user to save the JQL query. Then as stories are created in JIRA, the information is pulled as expected when the sync occurs.Users need an option for how the order of information displays
Users need an option for how the order of information displays. This selection should be an option a user can default so they do not have to pick each time they enter Zephyr Enterprise. Example 1: Today, ordering within several Zephyr Enterprise navigation folders were changed to display based on "last worked on" date. The enhancement would enable users to default to either an alphabetical display of folders (the prior version) or by date last worked on (the new version). Example 2: Drop-down lists do not always display items alphabetically for selection. Consider the page for sync requirements which displays two drop-down lists titled Field1 and Field 2. The drop-items do not display in alphabetical order. The enhancement would ensure all drop-down lists have a clear order for display and if that default option is not Alphabetical, users should be able to change their default option. Then the display would be alphabetical. It is expected that we can still type letters for a dropdown to quickly identify a value if it starts with "Z" for example, as that is how drop downs should work today.Users should be able to select the import folder for JIRA Gherkin test stories.
Today imported test cases (from JIRA Gherkin Test stories) are placed in a default folder in the test repository. The enhancement would allow the user to select the folder in which the imported test cases should be placed.Default the current Project for a user
After logging into Zephyr Enterprise, the user must select from a list of Projects. An enhancement is requested to enable a default project to be connected with the User's ID. It appears the "last project reviewed" is what is commonly displayed today. If no default is provided for the user, then continue with the current behavior. However, if a default is provided for the user, then that default project will display upon each login (instead of the last project the user navigated to see).Capability to add custom fields to Defect Tracking
In the Defect Tracking module there are two locations where an enhancement is requested to enable the use of custom fields. The first location is the search criteria for displaying defects. The enhancement would allow custom fields to be selected as part of the search. The second location is the list of defects that show as a result of clicking the search button. The user can select some columns to display on the list. The enhancement would allow users to select a custom field to display as a column on the list.
Ability to manage Test Cycle Environment Variable
Currently Environment variable is free text field in Test Cycle creation. We are looking for a way to manage this Environment variable as a Picklist to define existing available environments. Additionally a way to enforce it mandatory / non mandatory. This option would allow us to get the reports based on the Environments. Also support for the API to pass the environment vlaue during Automation Job creation https://cigna.yourzephyr.com/flex/services/rest/v4/upload-file/automation/create-and-execute-jobAdd versioning to ZE Internal Requirements
There is no way to quickly or easily tell if a ZE Internal Requirement has been modified or updated. After a requirement has been updated or changed, testers will often need to modify the mapped test case. Proposed Solution - Add version history to Internal Requirements and provide a way for the end users to tell if a requirement has been modified quickly through the UI and Search.Capability to move test cases within a release and to a different release is needed
To accomplish the goal of moving tests within a release or to a different release: 1) Consider how the test cases are selected for Movement. Selections are made in the Test Execution section (either the “all executions tab” or the “my execution tab” or the planning folder or through JQL) The selectoin must allow multiple selections at one time. Individually (but can be multiple selections) or By Folder or By Phase or By Cycle 2) Consider what needs to be moved with the Test Case: Execution Results Execution-Defect Mappings Execution Comments Execution Attachments Step Execution Results Step Execution Comments Step Execution Attachments 3) Consider how test cases move within a release. Selected test cases can be dragged and dropped to the chosen Cycle or Phase or Folder within that release. 4) Consider how test cases move across releases. It would require a pop-up box selection for Cycle, Phases, and Folder. Cycle and phases are required, but folder would be optional. The capability to create a new cycle and phase would be included. It would be nice to retain requirements mapping when moving to a new release.
