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.
Shipped | Next 1-2 Releases | Next 3-6 Month | Future | |
|---|---|---|---|---|
Detail View | ✅ Screen tab support, | Inline editing for custom fields | More inline editing | |
Tree view | ✅ Flexible tree structure, ✅ Custom ReqPath field | Display fields selector (for tree items) | Basic filter with more fields | Automatic Parent-Child linking, |
Reading View | ✅ Paste images | Display fields selector | Save selected display fields | |
Tabular view | Word wrap, Display fields selector | Save selected display fields | ||
Coverage View | Save selected display fields | |||
Traceability Matrix | Display fields selector (new) | |||
Revisions | ✅ Visual mode for rich text fields | |||
Baselines | ✅ Baselines in tree view, | Compare to current revisions | ||
Reuse | ✅ Folder attachments ✅ Issues in Epics | Visual reuse support | ||
Export | ✅ Consistent file names | Background export handling | ||
Migration Path - Server/Data Center to Cloud | ✅ Bulk ReqIF export | |||
and more features | Support for 3rd-party app custom fields | Use of permission schemes and supporting roles and users | Data model editor |
You are planning to go for R4J on Jira Cloud? Please see the comparison of R4J Cloud and Data Center features for latest update.
Not yet using R4J - Requirements Management for Jira?
Download it now and try for free for up to six months.
Want to know more about the features?
Contact our support team for more details.
Interested in being first in line to try new features?
We can invite you to join our beta programs.
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.