Requirement Yogi: Auto requirement numbering bug?

[David Griffin]

I'm evaluating this add-on and so far I'm happy with what it provides. However, I've just hit a snag, which isn't a blocker, but does impact one of the ease-of-use features, namely the auto-numbering when you alt+shift+r.

I created around 30 auto-numbered requirements, but then later decided I wanted to re-sequence the requirements, so I deleted all but the first requirement entry. When I then attempt to number the requirements again, specifying -002 as the first number, the resulting requirements numbering applied by Yogi starts at the -030 level. This is repeatable.

Is this the expected behaviour?

Is there a workaround I can use to reset the stored index number?

[David Griffin]

It turns out that it is necessary to save ('Update') the Confluence page and then go back into Edit before the deletion of requirement yogi requirements affects the sequence numbering of new yogi requirement tags.