Releases: SecurityRAT/SecurityRAT
Releases · SecurityRAT/SecurityRAT
v1.8.7
v1.8.6
Bug Fixes
- Fixed issue where link on Secrat Logo and Editor is incorrect when application is hosted behind a reverse proxy with its path ( #185 ).
- Building the frontend now works again ( #192 ).
- Jira ticket link is displayed without status in the requirement list when this link is inaccessible (e.g. due to missing rights)
Changes
- Use a HTML tag on the "View" button under the Browse all requirements interface.
- Various vulnerability updates.
v1.8.5
v1.8.4
Bug Fixes
- Fixed minor issue where displayed link to authenticate to JIRA (during import) is REST API link instead of origin.
v1.8.3
v1.8.2
Changes
- Switched from Java8 to Java11.
- Restructured the project:
- Separated frontend from backend.
- Now using maven multi-module project.
- Updated backend dependencies.
- Application is now released as JAR instead of WAR.
Bug Fixes
- Resolved an issue where creating Jira ticket (in batch mode) without labels did not work.
- Fixed issues when using SecurityRAT with a Jira instance running on a URL path.
v1.8.1
v1.8.0
Changes
- Switched from Java8 to Java11.
- Added a column in the requirement list view, which displays the selected artifact properties corresponding to each requirement. The visibility of this column can be changed using the constant showProperties in the admin interface.
- Restructured the project:
- Separated frontend from backend.
- Now using maven multi-module project.
- Updated backend dependencies.
- Application is now released as JAR instead of WAR.
Bug Fixes
- Resolved an issue where creating Jira ticket (in batch mode) without labels did not work.
- Fixed issues when using SecurityRAT with a Jira instance running on a URL path.