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?
Since our last roundup in April, Atlassian's Marketplace Partners have added over 100 new cloud apps to the Atlassian Marketplace to help your teams work more efficiently. Let’s take a quick look a...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events