Requirements and Test Management for Jira has just reached 1 000 installations. Our team is very proud and we would like to thank our customers for their trust and insight which both help us make our product better and better every day. We couldn’t have done it without you all. The success of our app made us feel a little bit nostalgic. This is why we’ve decided to share with you some curiosities about RTM for Jira. First, let’s dig into some statistics. Requirements and Test Management for Jira can show the following numbers off:

  • 1 000 total installs

  • 56 007 users with our extension installed on their Jira instance

  • 18 000 Test Executions run in the last 3 months

  • 5 600 Requirements created in the last 3 months

  • 5 600 Test Cases created in the last 3 months… it seems you have exactly 100% Requirements-Test Cases coverage  

Pretty impressive, isn’t it? Now, let’s move into some history! Are you ready to get into the time machine?

Shory story of RTM for Jira

Requirements and Test Management for Jira Cloud appeared on Marketplace on 08/04/2019. At that moment it wasn’t, in fact, a complete app, as it didn’t include all the features we’ve planned. Back then RTM for Jira only incorporated modules, like Requirements, Test Cases, Test Plans, Test Executions, and Defects. There wasn’t any report inside the app that could help teams collaborate. We wanted it to be the best testing extension possible and two years ago the leaders were far ahead of us. Nevertheless, RTM still had one thing that the competition didn’t provide: built-in requirements management. This was the factor that made us decide to release the first version of the product so soon. Moreover, we had some experience. At Deviniti there were two apps that supported testing so far: ReqFLO and TestFLO, which is still available and popular on the Marketplace.

ReqFLO – the first attempt of creating the requirements management tool

Starting with ReqFLO, our initial idea was to make the tool for requirements management only. There were lots of testing apps for Jira, but we found it strange how requirements were always excluded from the process. The teams stored them chaotically in Excel, Word, Confluence, etc. In order to support the workflow, ReqFLO was created. It had features like tree-structure for requirements, Traceability Matrix, export to a .PDF or a .CSV file. The teams found it really useful, it got lots of great reviews, but there was something missing, something else that can be done to really connect the requirements with the rest of the steps. The app was good, but it wasn’t enough. This is where we’ve decided to make a complete solution: Requirements and Test Management for Jira.

reqflo screen

New requirement screen in ReqFLO

The difference between TestFLO and RTM for Jira

Why couldn’t we just update TestFLO with the new functionalities? TestFLO was already known on the market as a fully customizable solution, which users can configure to make it fulfill the needs of even the most complex projects. We wanted to make RTM for Jira the most intuitive possible, as we thought that what was missing on the Marketplace was an easy tool to manage tests inside Jira. We focused on user-friendliness, consistency, and transparency of the consecutive steps. TestFLO is a tool meant for companies that require superb configurability, perform large-scale testing, and need support for automated tests out-of-the-box, whilst Requirements and Test Management for Jira aims to be the solution that allows starting work right after the installation. It enables all the testing steps even if the project is basic and the team is mostly on the entry-level.

testflo project configuration

Project configuration in TestFLO

rtm quick configuration

Quick configuration in RTM for Jira

People that stand behind RTM

Events

Events are one of the best parts. Not only you can travel and see beautiful places, but most of all, you meet great, inspiring people that motivate you to keep up the great work. With Requirements and Test Management for Jira, we started traveling in 2018. That time, we had an opportunity to participate among others in Atlassian Day in Budapest, Summit in Barcelona, StarWest in Anaheim, and EUROStar in Haga. In 2019 we visited Atlassian Summit in Los Angeles, celiX Solutions Day as well as Atlassian Open Europe in Vienna, and finally STAR Canada. 2020 was challenging for all of us on that score, but we still talk to people from the industry during online events. Here are some photos of these precious moments:

rtm event photo 1

We really tried to get your attention at any cost 🙂 :

The memories are priceless, but the feedback is equally valuable. The events made it possible for us to talk to testers, managers, analysts, and Jira admins. We’ve met very experienced and beginning colleagues. It helped us create an app that is not only user-friendly and easy to work with without any special training but also meets the expectations of complex projects and big teams. And we still benefit from your advice. Every step of the way we ask our customers and users what can we do to make RTM for Jira better. Remember that you can always contact our support to share your opinion and ideas. We also send e-mails once in a while to make sure everything works fine and you have all you need to release the best, bug-free products.

Reviews

When we don’t have the chance to meet you or contact you in person, the reviews come to the rescue. We are very happy to receive so much positive feedback from you, not only when it comes to the app, but also our support. Here are some of the most helpful, elevating reviews from our customers:

  • Great responses from the Support Team

  • Organization that simplifies the relationship between Requirements and Testing

  • Good usability, so you spend less time looking for where features might be and more time actually executing the work
    ~ Alicia Power

“I have tried our several testing tools and by all means, RTM is definitely the best tool that I have ever encountered that encapsulates quality in terms easy to write test cases, very smart test plans, and gradually reports in bonding the deliverables between QA and DEV in the most effective manner. Its strength is its simplicity, the re-enforcement between requirements and test cases, the bird eye view of basically any matrix view that one can imagine. “
~ Huseyin Ibrahim

We really like this add-on. It will suit our development workflow with requirements & tests management. I too have some recommendations.

Features:
– Execution view, being able to have the test cases in the same folder structure as in the test case management
– Execution view, being able to set the status of the test cases
– Execution view, being able to create defect (per test case, similar to execute)
– Defect creation, being able to create defect into another project and…
– …Configuration, being able to set up/show custom fields in defect

Bug/Improvement:

– Creating a jira issue with rtm-types (requirement, defect,..) shows the item in the table view, but not in the folder view on the left side
– Configuration view, “Disable RTM in current project” with a switch control is confusing. I’ll suggest either changing the control to a button or label to “Enable/Disable RTM…”
~ Mischa Zihler

Roadmap and plans for the future

As we’ve got all kinds of motivation coming from you, it’s easy for us to keep up the good work. Our team constantly works on new ideas in order to make Requirements and Test Management for Jira better. We’re improving the app’s performance even at a large scale, adding new functionalities, and making existing ones simpler to use. Here you’ll find our roadmap. The best part is that we made it possible for the viewers to vote for the features they find the most attractive and usable. There are four columns on the roadmap: Exploring & voting, In Progress, Done, and Leaving It For Now.

Exploring & voting
Things we consider interesting, but still under discussion.

In Progress
Functionalities which our brave team is developing at this very moment.

Done
Already implemented features.

Leaving It For Now
Some ideas that we came up with but ultimately decided not to continue working on (however, they can go back to the main stream anytime).

Everything’s in your hands! We believe that together we can make the perfect app.

Summary

In the last two years, we’ve learned a lot. We gathered testing knowledge scattered inside the company, added our experience gained whilst creating previous apps, and came up with a solution that is perfectly tailored to the needs of the majority of projects. We’re still working on more support for automation, which we believe is the future of testing, but still, our team is very proud of what RTM for Jira has achieved so far. Wish us luck, as we’re coming for the next thousand happy customers!