Page Comparison

...

• This will change in RY 3.0.
• We only accept a-z A-Z 0-9 and the three characters: . - _
• The reason is that we carry requirement keys in the URLs, and dealing with UTF-8 in URLs is difficult,
• Please avoid lone words for keys. Some customers use RY as a glossary, translating acronyms... That is not the intended purpose of Requirement Yogi.
• Unicity is guaranteed when inserting manually. There are corner cases where you may create duplicate requirements in a space (if you use an external plugin to create pages, for example); Requirements will appear in bright red with an error message to tell you to choose which one is the definition.
• Keys are unique per space.
• You can always create links across spaces by pasting the canonical URL of a requirement. You can only create links across spaces manually by searching in the Requirement macro, if you haven't ticked the option "Isolate spaces".

Traceability matrix

• To display Jira fields in the traceability matrix, tick the checkbox "Get data from Jira" at the top of the screen.
• Cells are limited and paginated, see the global limit in the Requirement Yogi administration.
• We have great renderers in the traceability matrix; However we don't have calculated fields. It means it is still difficult to track the % progress of a project for nowThe traceability matrix is paginated and can easily display 600 rows per page, on dozens of thousands of results,
• However, we don't support retrieving "too much" data from Jira, and pages need to be shorter as the number of Jira columns grow,
• Customers face problems when they want to export their entire matrix to Excel, which means it takes more than 2 minutes to extract the data from Jira. Requirement Yogi is not designed to pull the entire status of a project from Jira through the little pipe of communication between the apps.
• Workaround: Please investigate using EazyBI in Jira and retrieve the details of the requirements using our REST API.
• Also, we don't support calculated fields. It means we can't show the percentage of child requirements which match a given rule (for example, the % of requirements where the status is "OK", for the most usual usecase of tracking a project).
• As a conclusion, Requirement Yogi is designed to help structure the free text and track the requirements, but we are not a good project planning tool, and you would need an external BI engine for the project planning part.

Administration

• There is a queue of messages in Confluence and in Jira, that are transmitted to each other. This is designed to ensure that a user who doesn't have permissions in Jira can modify requirements in Confluence and have Jira updated.
• When installing the product, you must enter a username in both products for this queue.

...

• Requirements don't have a status.
• Customers manage the status by using a 

  Status
  colour Green title Status

  macro, and changing the text and colour manually.
• Customers also use EDM "Easy Dropdown Macro" to have a dropdown as a status.
• The drawback is, there is no validation of the permissions associated with the status change.
• The other drawback is, people do spelling mistake, and they can type "Valiid". We are planning on introducing a rules engine in the medium term. As usualy, please don't count on it until it is done and published.

...