Page History
Section | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Table of Contents |
---|
...
Panel | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
...
Panel | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
And more...
...
UX Improvements
- XRAY-7480: Export Execution Results - REST API should include Test Run Custom Fields results
- XRAY-1868: Whenever associating a Test Execution to a Test Plan using the REST API, the tests must be added to the Test Plan by default
Datasets
- XRAY-2892: As a user, I can obtain a list of recently updated Test Executions using a JQL function
- XRAY-2893: As a user, I can obtain a list of recently updated Test Plans using a JQL function
Document Generator
- 2273: As a user, I always create Test Executions in Xray using the Jira create issue dialog
- XRAY-5230: As a user, in the Test Run Page actual results section I can browse my local files
- XRAY-2799: As an Admin I can configure if the cloned Test case gets associated with the original Test Plan or Test Set
- XRAY-8258: When importing Cucumber JSON results, the evidence imported should appear in the overall Execution Evidence field, on the top of the Execution Details page
Notifications and Webhooks
- XRAY-7616: As a machine, webhooks are triggered whenever an Xray association is performed in Xray issues
- XRAY-3498: The event "Test Run Status set to Final" is not being fired
Datasets
- XRAY-7869: As a REST API user, I must be able to import an existing dataset from a CSV file
- XRAY-8439: As a user, I want the possibility to map a parameter from the parent test to the called testXRAY-6558: As an admin, I want to be able to define the maximum number of exports
Just one more, yet important, thing...
/ / TODO
All New Features and Bug Fixes in this release
...