299
Customers have installed this add-on in at least 299 active instances.
    by Optimizory Technologies Pvt. Ltd.for JIRA Server 6.0 - 7.2.1 and more versions
    Versions available for JIRA Server 4.0 - 5.2.11
    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Supported
    Optimizory Technologies Pvt. Ltd. supports this add-on.

    Get support

    Simplifying Requirements Management

    Simplifying Requirements Management

    Traceability between entities

    Control changes to requirements

    Integrated validation

    Establish traceability between requirements to other requirements, JIRA issues and test cases.

    Control changes to requirements through requirement versions and baselines.

    Users can define test cases and organize / execute them in groups as test runs.

    More details

    RMsis for JIRA is an enterprise class application, and used world over by 600+ customers. You should consider RMsis, if you are looking for a solution against any of the following challenges:

    • Managing moderate to large number of Requirements emerging from different sources.
    • Establishing and managing baselines to enforce agreements between multiple stakeholders.
    • Managing evolution of Requirements
    • Establishing, documenting and publishing forward and reverse traceability between Requirements as well as other artifacts.
    • Ensuring contract compliance in large and complex contracts.

    RMsis provides ability to

    • Define a flexible information model.
    • Create, elaborate, analyze and manage your requirements.
    • Create requirement baselines, versions and branches.
    • Establish cross project dependencies between Requirements.
    • Manage real time requirement traceability with JIRA artifacts and test cases
    • Plan and manage your key milestones and product releases.
    • Manage Requirements validation process

    RMsis Home

    User reviews

    (13)
    Sign in to write a review »
    by arasu mani on 2016-05-18
    Hi Optimizory Team, We are evaluating this plugin at my DEV environment where we use dummy SSL . Could you help me what should i fill in the place of "Keystore File" Thanks, Arasu M
    Was this review helpful?YesNo

    Optimizory Technologies Pvt. Ltd.

    Hi Arasu,

    We have sent you a mail from support (support@optimizory.com) and we will work with you to resolve your issue.

    Cheers !

    Optimizory Team.

    by Jose Acosta on 2014-02-26
    Does this plugin support folders for grouping requirements?
    Was this review helpful?YesNo

    Optimizory Technologies Pvt. Ltd.

    Hi Jose, In the current version, RMsis supports Hierarchical Organization of Requirements, where are parents are treated like containers (this is kind of folder view). RMsis also provides the possibility of creating Custom Hierarchical Categories, which can be used for a hierarchical grouping of requirements. If you need any further clarifications, please send a request to support@optimizory.com. Cheers ! Optimizory Team.
    by Ningning Tao on 2013-07-31
    A bit difficult to understand how to manage multiple project across the same platform. Updates: 1. Linking same version of 1 Requirement to Multiple Features in different JIRA projects (apply same requirement in multiple products) 2. Linking different versions of 1 Requirement to Multiple Features in different JIRA projects (apply same requirement in multiple products)
    Was this review helpful?YesNo

    Optimizory Technologies Pvt. Ltd.

    Hi Ningning,

    Recently we have done an introspection about the key issues / missing features of RMsis and this issue (reported by you earlier) has been identified as one of key issues. However, the impact of change is quite significant and hence the feature will be introduced with caution. Shortly, we will share an update with you.

    Cheers !

    Optimizory Team.

    by Jawad Habib on 2012-07-23
    Installed the trial version and have a few questions for the developers. Not sure if there is a forum for RMsis where users can discuss requests so I'm laying it out here: 1. Why do you specify "man-days" for the Effort field? It is just a numeric manual entry field with no effect on the burn-down or time-spent in JIRA. You would expand the appeal of this field simply by removing the "man-days" part. Agile teams, such as mine, could then put their estimates in "Story Points" or "Bananas" or whatever else fancies us. Man-Hours sort of confuses the not so savvy users. 2. When you run a report, say to view all stories, tests and other artifacts that are related to requirements, is there a way to group everything by requirement ID? That is, display one requirement only once and then under that group you can have versions, stories, tests and what not. Right now the requirement is repeated for each item that is linked to it. 3. When linking a requirement to a JIRA artifact from your traceability tab, creating a new artifact does not leave you with a way to go back to the requirement that you started with. You have to close the artifact window and then re-open the requirement from Traceability to make the association. I'm sure this would be an easy fix. Giving it 2 stars for now because the concept is good. I'm sure you will iron out the details to make it a 4 star plugin. ---------------- (07/23/2012) Updated rating to 3 stars due to promptness of Vendor's response. I will add suggestions to their CRM from now on.
    Was this review helpful?YesNo

    Optimizory Technologies Pvt. Ltd.

    Hi Jawad,

    We don't have a forum yet, but you can log suggestions / requests through the CRM (http://crm.optimizory.com/reportissue). These issues are tracked against your ID and are constantly reviewed for inclusion in forthcoming releases.

    Regarding your suggestions here, they are logged as RMI-926, RMI-927 and RMI-928 respectively. You can track their status after logging into the CRM (http://crm.optimizory.com/issues).

    All of these issues will be addressed in the next release. Expect it about 3-4 weeks down the line. Here is a short summary against each of the suggestions:

    1. OK, we will make the "Effort Unit" configurable.
    2. We have already developed "Expanded View of Traceability", which should fulfill your need. As far as the reports are concerned, they are generated as "Pivot Tables" for subsequent download and analysis. The suggested change is quite significant for us and we will take a decision after an internal discussion.
    3. This issue will be fixed. Thanks for pointing it out.

    Last but not the least, for any problems / suggestions, you can drop a mail to support@optimizory.com and you will surely get a prompt response.

    Cheers !

    Optimizory Team

    by Mickael THIEVENT on 2012-05-21
    I love this plugin. Installation is very easy, configuration is so simple and traceability is now well done with requirements, issue and test case. Some things are missed yet but Optimizory Technologies is very open and they answer everytime I suggested a feature, an improvement or a bug...and it's so nice to see our suggestions in a release.
    Was this review helpful?YesNo

    Pricing

    This add-on is sold by a third-party vendor.

    Let us know that you'd like to manage this add-on's billing on your Atlassian invoice.

    Paid-via-vendor pricing FAQ

    What does 'paid-via-vendor' mean?

    Paid-via-vendor add-ons are licensed and purchased directly through the vendor who makes this add-on.

    Payment for paid-via-vendor add-ons is not handled by Atlassian.

    Will paid-via-vendor transactions be on my Atlassian invoice?

    Paid-via-vendor transactions are not managed by Atlassian. This means transactions for paid-via-vendor add-ons will not be on your Atlassian invoice.

    Support

    Optimizory Technologies Private Limited supports RMsis - Requirements Management for JIRA. You can visit the support site to get help.

    Get support

    Versions

    Version 1.8.6 JIRA Server 6.0 - 7.2.1 Released 2016-08-17

    Summary

    Feature enhancements and bug fixes

    Details

    Detailed release notes for v.1.8.6-r297

    Important note

    • Shifted the RMsis links to bottom-right of issues page

    Requirements

    • Unlink all links to old version of a requirements

    Validation

    • Teststeps are added to the TC details

    Reports

    • Added tracking report

    Import / Export

    • Additional data exported with CSV and PDF

    System

    • Validated with JIRA 7.2 EAP
    • Feature to scroll up-down on list menu

    Key Fixes

    • RMI-4118 : Description of requirement missing in detailed view
    • RMI-4077 : Names of some columns missing in PDF
    • RMI-4002 / RMI-4000 : Test step window misbehavior
    • RMI-3993 : When linked bug is moved to other project, the association remains
    • RMI-3980 / RMI-3976 : CSV / PDF export issues
    • RMI-3970 : Duplicate requirements created
    • RMI-3942 / RMI-2436 : Remove restriction > 255 char in test steps
    • RMI-3161 / RMI-3766 / RMI-3767 / RMI-3768 : Issues with fields of type "Rich Text Area"

    Known Issue

    • JS error with JIRA 7.0.x. To resolve this please upgrade to JIRA 7.1.x or later versions

    Installation

    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate RMsis - Requirements Management for JIRA via search. Results include add-on versions compatible with your JIRA instance.
    5. Click Install to download and install your add-on.
    6. You're all set! Click Close in the Installed and ready to go dialog.

    To find older RMsis - Requirements Management for JIRA versions compatible with your instance, you can look through our version history page.

    Similar add-ons