Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Requirement Yogi: Auto requirement numbering bug?

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?

1 answer

0 votes

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

5 mobile apps for Jira Cloud to boost productivity

  It’s very important to have access to the workflow process from anywhere. Especially if you manage the work of others. There is no difference whether you’re out of office, or drive a ca...

260 views 2 5
Read article

Community Events

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

Events near you