...
- The current diff is limited to 600 requirements (=5% of the global limit, which you can configure).
- This is not enough for large customers with 12k requirements in baselines,
- It is a difficult problem to solve, but not impossible; We are hoping to solve it one day.
Requirement keys
- This will change in Before RY 3.0.:
- We only accept a-z A-Z 0-9 and the three characters: . - _
- After RY 3.0:
- Those characters are forbidden: / \
- We haven't noticed any character that caused an issue, but if we hear about it, we will write the inventory here,
- Requirement numbers can only reach +9223372036854775807. If you need higher numbers, please add another character in the middle.
- 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".
...