Get a rough overview on where we are heading to with R4J - Requirements Management for Jira. Please refer to the release notes for details about released features.
✅ Just Released
Tree Structure
| Expand | ||
|---|---|---|
| ||
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. |
| Expand | ||
|---|---|---|
| ||
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. |
Reading View
| Expand | ||
|---|---|---|
| ||
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. |
| Expand | ||
|---|---|---|
| ||
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. |
Revisions & Baselines
| Expand | ||
|---|---|---|
| ||
We rework reworked the way revision details are handled. This shall decrease the size of the revision tables drastically. |
Coverage View
| Expand | ||
|---|---|---|
| ||
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. |
| Expand | ||
|---|---|---|
| ||
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. |
Traceability Matrix view
| Expand | ||
|---|---|---|
| ||
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. |
REST API 2.0
| Expand | ||
|---|---|---|
| ||
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. |
▶ In the works
Flexible Tree Structure
| Status | ||||
|---|---|---|---|---|
|
▶ In the works
Performance Improvement
| Status | ||||
|---|---|---|---|---|
|
| Expand | ||
|---|---|---|
| ||
Supporting the loading time of large tree structures with additional configuration. |
| Expand | ||
|---|---|---|
| ||
With an optimized database setup, we support quicker search using our JQL function. |
| Expand | ||
|---|---|---|
| ||
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. |
Tree Structure
| Expand | ||
|---|---|---|
| ||
R4J is great to work with but every time you click on an issue key you are brought back to Jira? Not any more! We are improving the issue links in R4J to provide a standardized behavior. |
Export
| Expand | ||
|---|---|---|
| ||
We like the template based Word export – but as always, bridging tool borders isn't easy! So expect more improvements with the renderer for empty lines, anchors of attachments, mixture of text and tables, and {noformat} content. |
| ||
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. |
Cloud Migration Support
| Status | ||||
|---|---|---|---|---|
|
| Expand | ||||
|---|---|---|---|---|
| We are going to utilize Atlassian´s framework for our firstR4J versionin the Atlassian cloud ecosystem. More details can be found in our dedicated roadmap
| |||
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. |
ReqIF
| Status | ||||
|---|---|---|---|---|
|
| Expand | ||
|---|---|---|
| ||
Final release of ReqIF with enhancements from your feedbacks. |
📝 On the planning board
Tree
StructureFilter
| Expand | ||
|---|---|---|
| Expand | ||
| ||
| ||
Need more flexibility to structure your tree? We will soon allow to mix folders and issues on the same level! This should come with performance improvements to access the tree structure through REST API. |
📝 On the planning board
Export
| |
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. |
Template base Export
| Expand | ||
|---|---|---|
| ||
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. |
Administration
| Expand | ||
|---|---|---|
| ||
So far, you can control the access permissions with global Jira groups. We introduce support for project roles in the R4J permissions settings. |
Revisions & Baselines
| Expand | ||
|---|---|---|
| ||
Baselines should include additional details like folder structure and others to be an exact replica of the actual requirements. |
| Expand | ||
|---|---|---|
| ||
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. |
Permissions
| Expand | ||||
|---|---|---|---|---|
| So far you can control the access permissions with global Jira groups, now we introduce support for project roles in the R4J permissions settings
| |||
To specify the permission more accurate, new options will be introduced on global and project level. |
REST API 3.0
| Expand | ||
|---|---|---|
| ||
The REST API 1.0 and 2.0 offers lot of value to our customer. With the introduction of our R4J cloud version, an alignment of the API helps you to connect both worlds. Don´t worry, your scripts running on REST API 1.0 and 2.0 will work further on. We will not remove this versions and support will continue until further notice. |
| Info |
|---|
Not yet using R4J - Requirements Management for Jira? |
| Info |
|---|
Want to know more about the features? |
| Info |
|---|
Interested in being first in line to try new features? |
Disclaimer: This information is being shared in order to outline some of our current product plans. We are hopeful that the following can shed some light on our road map, but it is important to understand that it is being shared for informational purposes only, and not as a binding commitment. Please do not rely on this information in making purchasing decisions because ultimately, the development, release, and timing of any products, features or functionality remains at the sole discretion of Ease Solutions, and is subject to change.