Versions Compared

Old Version 3

changes.mady.by.user Adrien Ragot

Saved on

compared with

New Version 4

changes.mady.by.user Adrien Ragot

Saved on

Key

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

...

Info
titleWhen not to use it

People who use this screen will be tempted It is tempting to create massive numbers thousands of Jira issues . We don't recommend creating thousands of issues with it. Don't

create Jira issues in anticipation. Only create issues for tasks that you are going to perform during the next Sprint.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

. 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 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.
This screen is very useful when planning development work, but it won't help if you are trying to maintain the same information in Confluence and Jira
  • . 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.

How it works

explanationscreenshot

Start from the Search screen, select a set of requirements and click on 'Create Jira issues'.

Note: The limit by default is 2000 requirements. It is defined by the global limit, available in the administration.

Click on the blue plus button to create a new issue template.

Template configuration:

  • Select a Jira instance.
  • Select a project.
  • Select an issue type.
  • Select a relationship.
  • Pre-configure fields.

If the checkbox 'Group all in one link' is checked, it will create one issue for all the selected requirements, otherwise, it will create one issue per requirement.

You can use some keywords to configure the issue's fields:

  • {key} will be replaced by the requirement's key.
  • {text} will be replaced by the requirement's text.
  • {baseline} will be replaced by the requirement's baseline number.
  • {relationship} will be replaced by the issue template's relationship.   

Note that these reserved keywords will be ignored if you create one issue for multiple requirements.

Once an issue template is created, you can re-configure it. Note that only fields are editable. 

If you wish to change the project or the Jira instance, you will have to create a new issue template.

Select requirements and Drag and drop into an issue template and click on create issues.


Once issues are successfully created, they will appear on the right sidebar.

...