DATA CENTER AND SERVER | CLOUD

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

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 Filter

 Simpler filtering of the tree structure

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.

Flexible Tree Structure

 Any order of folders, issues, and pages

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

 Use ReqIF for tree structure migration

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.

Tree Structure

 Expand all is back

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.

 Tree structure

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.

▶ In the works


Revisions & Baselines

 Show tree structure in baseline

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

 Formatting display options for the comparison and baseline views

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.

ReqIF ON REQUEST

 General availability of ReqIF ex- and import

Final release of ReqIF with enhancements from your feedbacks.

📝 On the planning board


Template base Export

 Roundtrip support for Word and Excel export

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

 Use project roles in permission administration

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

Permissions

 Extend the permission handling for baselines and coverage view

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

REST API 3.0

 Alignment with the Cloud REST 3.0

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.


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.

  • No labels