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
Revisions & Baselines
| Expand | ||
|---|---|---|
| ||
We rework the way revision details are handled. This shall decrease the size of the revision tables drastically. |
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. |
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. |
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. |
▶ In the works
Revisions & Baselines
| Status | ||||
|---|---|---|---|---|
|
| Expand | ||
|---|---|---|
| ||
We rework the way revision details are handled. This shall decrease the size of the revision tables drastically. |
| title | Formatting display options for the comparison and baseline views |
|---|
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. |
Cloud
| Status | |
|---|---|
|
| Expand | ||
|---|---|---|
| ||
Final release of ReqIF with enhancements from your feedbacks. |
Cloud
|
|
| 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. |
ReqIF
| Status | ||||
|---|---|---|---|---|
|
| Expand | ||
|---|---|---|
| ||
Final release of ReqIF with enhancements from your feedbacks. |
Tree Structure
| 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
| Expand | ||
|---|---|---|
| ||
Supporting custom fields for more data visibility and insights into your shared Word and Excel exports . |
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. |
Administration
| 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. |
| 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.