easeRequirements - Requirements Management for Jira (R4J)

Does not create or update real links between issues. The requirements tree lives inside the Add-on only and hence it is completely useless in other parts of the Jira. You can’t JQL it, you can’t add detailing requirement to the sprint, you can’t organize your reqs into tree of links or subtasks. The only use I can see here is traceability matrix. However, there are other add-ons doing it better. And I was hoping to get a comprehensive tool for describing and fulfilling requirements for the first time.

• 

  Ease Solutions Consulting GmbH

  Dear Evgeny, we appreciate your feedback to our product. The requirements tree of R4J allows you to further structure your project requirements in addition to JIRA issue links. You can query this structure using JQL as described here: Advanced Search. We would be happy to invite you to a web-based demo session to demonstrate the features and to discuss how they can be used to fulfill your needs. Please create a ticket in our service desk and one of our consultants will get in touch with you to schedule an appointment.

Is there support upcoming for cloud edition?

• 

  Ease Solutions Consulting GmbH

  Dear Roland, we currently don't have this on our roadmap due to technical limitations in the Cloud API. However, Atlassian has recently announced a new framework for this and we will re-evaluate once there are more details available. Please do submit a support request in our portal for any more questions or clarifications, our support team will be glad to communicate with you. Thank you!

Our team is currently building up requirement and test management and the R4J and T4J plugins have already shown their great value. One of the reasons why we have chosen those plugins is the possibility to reuese requirement issues in different projects. This is useful for our team as we have different projects/products that share many requirements. The only thing I'm currently missing is the possibility to import a project's complete requirement tree (including folders and issues) to another project. I have figured out how to import all exisitng issues of a project using a jql query. However, after importing them the new requirement tree is flat as the folder structure does not get copied.

• 

  Ease Solutions Consulting GmbH

  Hello Simon Berger,

  thank you very much for your inspiring review. I would like to guide you to our Re-Use documentation to solve your issue with importing a complete requirement tree in another project. In the reuse dialog please select NO at the "Create link to new issues" option, so the complete structure (folders) is copied, but the nested requirements are only linked. If you need help with this process, please contact our support team.

R4J has satisfied majority of the needs that we have in our management system. Nice coverage view and traceability matrix is just good. I should also admit the Revision concept is awesome. There are always something more to ask from R4J in the product and here I should admit that support team is always in the forefront to reply with acceptable answer and is very prompt. Keep it up R4J.

• 

  Ease Solutions Consulting GmbH

  Dear Alok, thank you very much for this comprehensive review. Was great to talk with you, thanks for your valuable input for our next R4J versions.

Nice Plugin, could be integrated within Jira as Application if business goes well. I have a question concerning the export to Word using the template-language. How to conserve the Word Template Style applied to the template-language expressions such us ([[\wiki $,description]][[wiki]]) ?