Add 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.
Requirements permissions need refinement
The requirements permissions option gives more permission than some users should have simply because they need to use the map button. Additional options are needed to refine capabilities beyond delete. The Jira requirements option is the best example as to why this feature is needed. Only select people should be able to bring in requirements, but more people should be able to map. The proposed change (feature request) would offer more options as follows: 1) Read only (includes Export Requirements, map button) 2) Read/Write Only 3) Read/write Delete (with Jira Sync config, Jira sync Requirements, and disable sync)
Adding Graphics
We would like to be able to upload image files directly to Zephyr opposed to users having to save them to their local network folders prior to adding them as attachments. This would allow for a more central location of storing the images and a more seamless experience for our end users who believe the current method slows down their testing process.Edit Test Case button always displayed on Test Execution panel
I’m executing a lengthy test script and I’m updating it at the same time. I find myself regularly pressing the Top button to access the Edit Test Case button, making then saving an edit, and then having to scroll back to the individual steps. I suggest making this button easier access by having it always visible on the interface.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.
