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.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)