If you're using Jira 9 and want to upgrade to Jira 10, a manual installation is required for the first time.
Download the Jira 10 compatible app version from the Marketplace.
If you're using Jira 9 and want to upgrade to Jira 10, a manual installation is required for the first time.
Download the Jira 10 compatible app version from the Marketplace.
Jira 10 compatibility along with a series of bug fixes and enhancements!
|
Component | Issue Key | Summary | ||
|---|---|---|---|---|
| 1 | Jira Compatibility | EASE-20585
| Jira 10 compatibility for easeRequirements Standard and easeRequirements Ultimate. | |
| 2 | Project Activation | REQ-17586 | Select how to activate projects with the following options in the revamped “Activate Projects” page (within Manage apps):
| |
| 3 | Project Archiving | EASE-11832 | Disable archived projects in the improved project activation page and easeRequirements project list. | |
| 4 | Display Fields | EASE-9344
| Persist selected fields in the display fields selector per user, project, defined issue type and folder. | |
| 5 | Coverage View | EASE-19054 | Added current project to JQL source when configuring a new view or column of the coverage and traceability views. The user is now guided to use the project condition to ensure better performance. | |
| 6 | Revisions | EASE-20144 | Added issue revisions when changing the “Epic Link” Jira field value. | |
| 7 | easeRequirements Ultimate | EASE-19293 | Combine data from two baselines into a new baseline. Read more | |
| 8 | easeRequirements Ultimate | REQ-16522 | Revert issue field values to the values in the selected baseline. Read more | |
| 9 | easeRequirements Ultimate | REQ-17269 | Add a public coverage view as an item in the project tree for more efficient requirements analysis. Read more |
Bug fixes
Component | Issue Key | Summary | |
|---|---|---|---|
| 1 | Coverage View | EASE-20236 | Fixed bug where the coverage view table does not display all issues. |
| 2 | Coverage View | EASE-20277 | Fixed JQL source error in the coverage view's column configuration when using ampersand '&' on folder name and custom field name. |
| 3 | Coverage View | EASE-20330 | Fixed bug in coverage creation via REST API 1.0 – |
| 4 | Coverage View | EASE-20517 | Fixed failure to create coverage statistics in the coverage gadget. |
| 5 | Coverage View | EASE-20335 | Fixed bug where Parent Link issues from Advanced Roadmaps for Jira do not show in the coverage view. |
| 6 | Excel Export | EASE-18215 | Fixed tree Excel export error when using a Macro-enabled Excel custom template. |
| 7 | Excel Export | EASE-18681 | Fixed incorrect order of issues in tree Excel export when exporting a parent issue with multiple child issues at different levels. |
| 8 | Word Export | EASE-17252 | Fixed missing field values in tree Word export using an export template that contains custom field names with special characters, e.g. bracket, quotation marks, dash, etc. |
| 9 | Word Export | EASE-17528 | Fixed incorrect values in tree Word export using an export template that contains “currentIndex” expression within a “variable” statement, e.g. |
| 10 | Export Template Configuration | EASE-18735 | Fixed bug where a Word export template that contains an expression with missing brackets can be uploaded without showing any error in the export template configuration. |
| 11 | Tree View | ADMIN-348 | Fixed wrong issue type values provided when selecting a different project in “Create Linked Issue” dialog in the tree view. |
| 12 | Suspect | EASE-17686 | Fixed bug where the suspect value is copied when cloning an issue in Jira. |
| 13 | General | EASE-20176 | Fixed workflow operation error when transitioning the status of issues created in Jira. |