...
This release is especially focussed on the TC module, "Testing & Compliance". We're introducing:
| Jira Legacy |
|---|
| showSummary | false |
|---|
| server | JIRA |
|---|
| serverId | c44f7f6b-309d-3e24-ae45-f50de66a98eb |
|---|
| key | RY-256 |
|---|
|
When running a test session, we can now add comments and raise Jira issues along with the pass/fail result.| Jira Legacy |
|---|
| showSummary | false |
|---|
| server | JIRA |
|---|
| serverId | c44f7f6b-309d-3e24-ae45-f50de66a98eb |
|---|
| key | RY-202 |
|---|
|
For people who don't have Requirement Yogi and who write requirements in Jira (X-Ray users, namely), it is possible to create a test session based on the results of a Jira query.| Jira Legacy |
|---|
| showSummary | false |
|---|
| server | JIRA |
|---|
| serverId | c44f7f6b-309d-3e24-ae45-f50de66a98eb |
|---|
| key | RY-255 |
|---|
|
It is possible to copy and reset a test report, in order to run it again.
Minor fixes:
| Jira Legacy |
|---|
| showSummary | false |
|---|
| server | JIRA |
|---|
| serverId | c44f7f6b-309d-3e24-ae45-f50de66a98eb |
|---|
| key | RY-266 |
|---|
|
Bugfix: In RY Reports, null cells would contain the previous value instead of being empty.| Jira Legacy |
|---|
| showSummary | false |
|---|
| server | JIRA |
|---|
| serverId | c44f7f6b-309d-3e24-ae45-f50de66a98eb |
|---|
| key | RY-265 |
|---|
|
Ability to transform a table into requirements by selecting cells. It brings the flexibility that the RY macro can be created in the second column, or that the RY macro can reuse the contents of the cell if they already contain requirement numbers.
...