Versions Compared

Old Version 22

changes.mady.by.user Adrien Ragot

Saved on

compared with

New Version 23

changes.mady.by.user Mileva Briand

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

✅ When to use it

❌ When not to use it

This new screen is particularly useful in the following situations:

  • If you are in a Sprint meeting and you are planning development tasks, you will select a few requirements, and create Jira issues for them.

  • If you want to associate each high-level requirement with a validation workflow, and have each single one be approved by a manager, a board of stakeholders or testers,

  • If you use Xray and you want to copy all Confluence requirements into Jira requirements.

It is tempting to create thousands of Jira issues with it. Don't. You will then have questions about keeping those issues up-to-date with Confluence, or across baselines. The goal is not to copy the entire Confluence database into Jira. In fact, we've limited to 100 600 Jira issues per batch for the moment, until we improve scaling.

  • It is much better to link a Jira issue to an entire page, rather than link an issue to every single requirement in it.

  • Creating 1 Jira issue for each requirement is a sign that you are managing the same data as requirements and as Jira issues.

  • It slows down the instance if you need to update a batch of Jira issues each time you update a Confluence page. We're happy to sell consulting services to diagnose and improve your performance, but it is a painful problem to have, and we've already optimized the product a lot. If you have the same data in Confluence and Jira, you should choose only one product.

The value of Requirement Yogi comes from annotating free text. If you keep transforming free text into Jira issues, you are making it painful for you to manage requirements. Perhaps don't create Jira issues in anticipation. Only create issues for tasks that you are going to perform during the next Sprint.

...

  • The templates limit is 30 per space.

  • You can't group more than 20 requirements in one Jira issue.

  • We truncate the summary to 253 characters because this is the Jira limit.

  • The left sidebar is and right sidebars are paginated and will display 600 requirements per page.

  • If you don’t know which requirements you have already created Jira issues from, tick the "Hide Synchronized” box to show only requirements that you have not linked to the templates created.

...