Versions Compared

Key

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

...

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 with the requirement's key.
  • {text} will be replaced with the requirement's text.
  • {baseline} will be replaced with the requirement's baseline number.
  • {relationship} will be replaced with the issue template's relationship.   
  • {@any_property} will be replaced with the value of 'any_property'. Unlike the search syntax, you don't need to escape special characters here.

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.

...

  • 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.,
  • We truncate the summary to 253 characters because this is the Jira limit.

Right sidebar

  • When selecting a template, the right sidebar shows issues created using this template.
  • If you want to reapply the template to existing issues, drag them from the right sidebar to the template. Their fields will be updated like in the template.

Limitations

  • We support some multivalue fields such as Jira labels. However, we don't support the Components field, which looks like a Jira label but is technically different.
  • If you put a property for the labels, such as {@requirement_category}, it will be replaced.
  • If you put a property of type "list" for the labels, such as {@requirement_categories}, it will not be expanded. It will write the full list into a single label, instead of inserting n labels like one would expect.