...
If you want to find a specific issue, we’ve now introduced a search bar. You can look for issues by key or summary
When selecting a template, the right sidebar shows issues created using this template. This option fetches and caches Jira issues (only issues with the same project and issue type are cached to limit performance issues) then it uses the cache to find Jira links to issues matching the selected template (same project, same issue type, same relationship name). The timeout for Jira Issues retrieval is 5 minutes.
If you want to update Jira issues, you can drag an issue from the right to the template. Their fields will be updated like in the template.
If you have manually created a Jira issue and linked a requirement to it, you might want to find it in the Jira Bulk Issue Creation search and apply the template to it. If you look for its key in the search and it does not show, tick the "show similar box”" box. As the issue was manually created, it does not have a template id. To apply a template to it, drag the issue on the template and the manually created issue will now have a template id → the issue will be updated as if it was created by the template. If an issue has more than one link, this process fails (as before, because we don’t know how to replace the templated values).
...
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_categoriescategories}, it will not be expanded. It will write the full list into a single label, instead of inserting n labels like one would expect.
...