Requirements Yogi database inconsistency


Hi there,

currently one of our customers has problems with duplicated entries within the RY database.
It seems that two requirements are created with one ID (RY - duplicated Keys.png), when a page is in draft mode or at least a draft is saved somewhere. Unfortunately we were not able to reproduce this issue manually, but still this happens automatically. Even if one of those keys has been deleted, both will not be shown on the screen, however, when adding the same key again (in our case "EST_TSP_F-0001_UC_002"), the new one and the corrupted one will be shown again. Furthermore you can also see the text "this requirement was inserted by a user on a draft, but the page hasn't been created yet." however, there are no draftpages anymore.

Additonally you can also see (RY -fields out of sync.png), that some of the fields are not synct correctly after renaming requirements. We assume however that this is also related to our first issue.

Do you guys have any idea how to fix this? Is there a way to clear the RY database tables somehow?

Also when you try to rename requirements, the "long running task" will not disappear automatically. You have to switch to another page and hope that the long running task has been completetd successfully.

Looking forward to hear from you guys







Matthias Schouten
April 10, 2018, 6:37 AM

Hi Adrien,

When renaming a Requirement the attached lists are shown.

We use two different Confluence spaces, the issue was observed in space 2.
I can see different lists of messages for the spaces.

The requirements document containing the duplicated definition of the RY objects is not in the list, nor any other document containing references from/to that requirements document or other RY objects.

Do you have any recommendation on what to do regarding these messages?

Btw, would it be helpful to have a teamviewer session regarding this issue?

Kind Regards,


Adrien Ragot (Old account)
April 6, 2018, 2:30 PM

Hi Matthias,

  • I can't reproduce the issue either,

  • Everything is already protected against name collisions, when renaming requirements or when creating new ones,

  • It may not be related to a draft. This message shows when the "host page" is missing for a requirement, because this is where it happens most frequently. However, in this situation, it's caused by the duplicate name.

  • Do your customers sometimes view the page history? I suspect the error messages in the logs are those that might display when viewing the history of a page, or maybe on a special object (comment, blog post, maybe an attachment, they can all be considered "content"), although I can't be sure.

  • If you have the opportunity to tell me what are the two pages references in the error message of the long running task, it would be great. Are those blog posts or special objects, or are they actual pages?

In any case, I suggest:

  • I'll merge requirements with the same name. It means the first requirement will also get the properties of the second one, and the second one will be deleted.

  • I'll perform this detection of duplicates in an upgrade task, which means it will happen when you install the next version of the add-on. I'll also perform it each time one saves a requirement, so errors are fixed as early as possible.

Best regards,

Matthias Schouten
March 23, 2018, 6:09 AM

Just saw that I missed out to set the priority right. This is in fact a "Matter of days" Issue, as the customer is not able to work properly with RY anymore.





Matthias Schouten






Fix versions

Affects versions


Matter of months