| Status | |||
|---|---|---|---|
|
...
We’ve created a new configuration to use with the macro: Requirement Configuration.
If your requirement page is structured like: Parent requirement definition, and all other requirements defined in the page are actually children.
Put the Configuration macro at the top of your page, or your table.
Go to the Parent Configuration, and choose the relationship name you desire.
We take the first requirement of the page as the parent, when there is only one requirement defined in the table (ex: a vertical table, or a paragraph), we’ll index it as a parent of all following requirements.
What your document looks like: | What we index: |
|---|---|
  |
|
| Status | ||||
|---|---|---|---|---|
|
We have improved the External Properties type ‘Dropdown’ and made it possible to add multiple values.
  |  |
| Status | ||||
|---|---|---|---|---|
|
We’ve released a graphical way of seeing your requirements. In the requirement detail, at the bottom, check your the dependency graph to see, at a glance, parent and child requirements, and Jira issues.
...
| Status | ||||
|---|---|---|---|---|
|
Please note that this is still BETA.
We have developed the export and import of Baselines from your Server / Data Center instances to the Cloud. The main use case is when you are migrating from Server to Cloud.
It is possible to export your Baselines from Server / Data Center.
It is possible to import these Baselines to the Cloud.
⚠️ However, those Baselines will not be visible in the Cloud yet. We are working on the Baselines feature on the Cloud, but it will take a few months to be released.
If you are planning to migrate now, you can export your saved baselines and import them on the Cloud, you will just have to wait a couple of months to be able to see them back in the Cloud.
Minor Enhancements
Transformation wizard
Reverse transformation improvements
UI/UX
Traceability
UI/UX
Requirement types
Search tab improvements (pagination)
Jira and requirement links