Versions Compared

Old Version 1

changes.mady.by.user Salmane Hmiza

Saved on

compared with

New Version 2

changes.mady.by.user Adrien Ragot

Saved on

Key

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

A lot of users requested an easy way to create issues in bulk and link them to requirements in Confluence. We are happy to announce it is finally possible.  

Tip
titleWhen 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.
Info
titleWhen not to use it

People who use this screen will be tempted to create massive numbers of Jira issues. We don't recommend 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.
  • It is much better to link a Jira issue to an entire page, rather than link an issue to every single requirement in it.
  • 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.

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.

Image Modified

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

Image Modified

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.

Image Modified

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


Image Modified

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

Image Modified



Good to know

  • The templates limit is 30 per space.

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

  • You can also drag and drop issues from the right panel to modify them.

  • The When selecting a template, the right sidebar show shows issues created by the selected issue using this template.