Saved filters and JQL are a great way to reduce your tree view to the issue you need to manage. This will be extended by an easy-to-use quick filter option like you know from the Jira Basic search.

We are adding invisible marks to the MS Word document. So you can get to know which issue keys the field values belong to. This will be used from our Word plugin to allow a round trip with Jira.

The Excel Export need modifications to support a true round trip, this will be supported by a few additional configuration options.

So far, you can control the access permissions with global Jira groups. We introduce support for project roles in the R4J permissions settings.

Baselines should include additional details like folder structure and others to be an exact replica of the actual requirements.

So far the comparison and baseline view only shows the plain text for rich text fields. Soon you will be able to compare the rendered text.

To specify the permission more accurate, new options will be introduced on global and project level.

The tree structure can be expanded by one, two.. and all levels. To avoid loading delays, your admin can define the maximum number of levels.

Hard work done to speed up the tree loading, export, and usage of filtered structures. Don’t forget about warped speed for retrieving issues from a folder using our Advanced JQL.

We´ve changed the technology used to show the reading view. Now, you can scroll smart through your data. Only visible data is loaded to your browser.

Now, you can create new issues, folders, and so on from the new context menu. The tree and the reading view share the same menu.

We reworked the way revision details are handled. This shall decrease the size of the revision tables drastically.

The coverage view speeds up now! We improve the loading and filtering performance, especially for large tables. If you want to access specific issues listed in a column, just click on the header.

The coverage view offers you a flexible view using different system and custom fields. Now, you are able to add these display fields also to the coverage export template.

The coverage view supported it already. Now, you can also view and modify the relations between Jira Epics and any kind of issues directly from the traceability matrix.

The REST API 1.0 offers lot of value to our customer – to extend features and functions, we introduce REST API 2.0 which aims to provide a more complete and better structured REST support for R4J.

If you have scripts running on REST API 1.0, no need to worry! We will not remove this version and support will continue until further notice.

Goodbye fixed order for these types of artifacts. The tree view and reading view allow you to arrange them in the order you need to explain it to your users. Inside a project, you can start with a Confluence page describing the idea, add issues to reference to the project targets, and then start with the folders holding the marketing and product requirements. Finally, provide a Confluence page again with the glossary.

The Atlassian migration tools are a great help to transfer your issues into the Cloud. Use our bulk ReqIF export to transfer over the tree structure including folders.

Final release of ReqIF with enhancements from your feedbacks.