What do you like best about the product?

The main thing I like is that almost every item in Jama Connect has an associated URL, which makes it very easy to share any item through that URL, and for other users to refer back to that item. The second-best thing is that there is no practical limit to the number of stakeholders that can have read-only access to the requirements. The versioning of items is also very good, together with the establishment of baselines for the requirements, both to help with releases, and be able to easily compare between those baselines/releases. The Review Center, although it has not displaced the existing Jira-based review that already existed in our organization for established documents, we have used it successfully for new documents/requirements outside of the established process. Finally, you can tailor the existing item types and relationships, and create new ones, with standard types for requirements management and testing as part of the default set. Jama Connect is essentially a malleable database that we can use to solve our needs in requirements management, traceability, and compliance.

What do you dislike about the product?

Sometimes the speed of some of the screens/interfaces could be improved. Relationships are not easy to be imported or exported, that's a difficulty we have found a number of times, specially when starting from a set of requirements coming from a document. And reporting is sometimes difficult to prepare. It would be good if there could be some wizard/screens to help you create reports (both Office-based and Velocity Engine-based ones) and visualize the reports online based on the different fields that you might want to display, and/or different operations.

What problems is the product solving and how is that benefiting you?

Jama Connect for Requirements Management solves for us the traceability from science to system technical requirements, ensures also compliance flow, and we hope to use it to store verification plans. We will be able to run test campaigns which will be linked directly within Jama, keeping our compliance up to date.

What do you like best about the product?

I like that Jama Connect for Requirements Management is web-based, which means its performance is not dependent on my hardware, and the database is safely stored in the cloud instead of on my laptop. I appreciate that everyone receives updates automatically because everything is online, eliminating the need for manual pushing or committing changes. The customer service experience is something I really like—it is efficient and very helpful, providing assistance to a great level of detail. Additionally, I found the initial setup to be intuitive and I love the well-designed, user-friendly UI, especially with my previous experience with tools like Doors, Jira, and Cameo.

What do you dislike about the product?

The export to Word, Excel, PDF is not working so well. Duplicating requirements is not optimal. Changing item types is not optimal. Deriving statistics is not optimal. If one could make batch changes to specific parts of the requirements or tests, that would be great. It is possible via the API, but that requires too many skills that the average user does not have. It is expensive, and we would love to use it with Capella, but the interface is not free.

What problems is the product solving and how is that benefiting you?

Jama Connect for Requirements Management enhances traceability, serves as a single source of truth, and frees us from dependence on MS tools. It efficiently defines requirements and corresponding test cases at both user and engineering levels.

What do you like best about the product?

What I appreciate most is the live traceability feature. Additionally, the review center for requirements is also excellent.

What do you dislike about the product?

I am working on a large project in Jama Connect using the Gherkin format, and I have noticed that load times can be problematic for very big projects.

What problems is the product solving and how is that benefiting you?

It addresses the challenge of tracking and managing the requirements of a complex project in a very systematic way. I prefer this tool over Jira.

What do you like best about the product?

Very useful tool to get the requirements for my products

What do you dislike about the product?

Has some learning curve. But after that, it's a very easy tool

What problems is the product solving and how is that benefiting you?

I use is to write and review product requirements and also register test cases and test results

What do you like best about the product?

Allows live interaction with growing requirement complexity systems. Especially critical at the beginning of the design phase.

What do you dislike about the product?

Manageable integration, but however representing a significant effort, especially with 3rd party tools. Cost of license high.

What problems is the product solving and how is that benefiting you?

complexity of requirements. Dependence in child and parents requirements

What do you like best about the product?

We primarily use Jama Connect for defining software requirements. The tool offers several features that I particularly appreciate:

1. Administration & Implementation
The system is easy to configure. You can define general settings that apply to all projects—such as permissions, item types with required fields, workflows, and relationship rules.... At the project level, you can select the necessary item types and, if required, override permissions or workflows.
It is straightforward to maintain consistent behavior across projects. Additionally, configuration changes can be applied centrally, affecting all projects at once.

For reporting, Word/Excel templates can be created quickly and easily, although they come with certain limitations (e.g. you cannot aggregate information). More complex reports can be generated using Velocity templates, which can be challenging for beginners and it is time consuming.

For integrations, Jama Connect provides a well-documented API that allows you to retrieve, update, or create objects (including configuration objects, requirements and test items).

2. Requirement Structure & Definition
Requirements can be organized into Components, Sets, and Folders. A Set corresponds to a specific item type. Moving requirements between folders is simple, and item types can easily be converted into others. This flexibility is especially helpful during the initial implementation phase if you need to adjust the structure.

The Excel Roundtrip feature is particularly useful when working with item types that have many fields to update. (Note: For description fields, you must define them in HTML format, which is slightly more complex.)
Importing requirements from Excel or Word works well, provided the source document is well structured with headings. All imported items initially share the same item type, but you can easily adjust this afterwards.

3. Review Functionality
The review feature is excellent. You can send a batch of requirements for review and assign specific reviewers. Reviewers can highlight text within the requirements and add comments. These comments can be tracked and filtered, and once they are addressed, they can be marked as resolved. You can also compare changes between review versions, provided that the same items are included in the same review. This means you need to manually manage the items in review-items, for example using filters.

4. Finding & Exporting Data
Requirements can be filtered easily using keywords or predefined filters. The export functionality is very convenient—especially the context-sensitive export, which allows you to export exactly what is visible on your screen.

5. Testing Features
Jama Connect also supports creating test plans, test cases, and test cycles, as well as executing tests. However, we have not yet made extensive use of these capabilities.

6. Support
During the initial setup, we received excellent support, and the system was ready for use very quickly. Integration with the cloud application and SSO also worked smoothly. Whenever we open a support ticket, we receive fast and helpful responses.

What do you dislike about the product?

Jama Connect is a requirements management tool, not a project management tool. However, I do miss the ability to plan requirements and track progress directly within the system. This can be worked around using the API or by exporting data to Excel and managing progress tracking externally.

When creating filters, there is currently no way to organize them into a hierarchy. Filters are automatically sorted by item type and name. Over time, as the number of filters grows, this makes it harder to keep track of them—so establishing clear naming conventions is essential.

Regarding license management, the unlimited stakeholder licenses for viewing requirements and performing reviews are a great benefit. However, when a user with a creator floating license is login and if all floating creator licenses are in use, that user is automatically downgraded to a reviewer license. In that case, they can only access requirements that are part of a review and lose visibility of all others.

The search functionality works in a traditional keyword-based way. However, users are increasingly accustomed to conversational, AI-like querying (similar to ChatGPT), which is not yet natively supported in the tool.

What problems is the product solving and how is that benefiting you?

In the past, all requirement-related information was scattered across Jira, Confluence, Word, and Excel, making it difficult to know whether anything was truly up to date.
With Jama Connect, we have centralized most of this information into a single, reliable source of truth. The transition is still ongoing, but the shift in mindset is already bringing greater clarity, consistency, and confidence to our work.

What do you like best about the product?

The flexibility in customizing the flow and content of requirement, while still maintaining some simple proces flow. The traceability and build in (visible) versioning is also powerful.

What do you dislike about the product?

While the requirement management is build around reusability, Test management in Jama, doesn't work quite well when we want to reuse and parameterize test cases.
We have many products where we want to run the same scenarios, in multiple configurations. As we would like full traceability some of these configuration would amount to more than 1000 test multiplied by the different feature scenarios we have multiplied by the different servers. So this quickly becomes thousands of different test cases.

What problems is the product solving and how is that benefiting you?

Jama Connect is solving two issues right now. Traceability and product requirement overview, in one tool. This is giver a good overview of how our products are working and how they are suppose to work, how well each feature is tested and what corner scenarios we aren't testing yet.

What do you like best about the product?

What I like best about Jama Connect is the ability to maintain traceability between requirements, tests, and defects, which helps ensure complete coverage and supports impact analysis during changes.

What do you dislike about the product?

The search functionality in Jama Connect could be more advanced. It sometimes lacks precision and flexibility, making it difficult to quickly find specific items or filter results effectively.

What problems is the product solving and how is that benefiting you?

Jama Connect helps ensure traceability between risks, requirements, tests, and defects, which is essential for compliance and impact analysis, making collaboration more efficient.

What do you like best about the product?

What I like about Jama Connect is the centralization of the ressources and documents and the shared visibility with other project members.

What do you dislike about the product?

One thing I dislike about Jama Connect is that the user interface can feel a bit unintuitive at times, especially for new users. It takes some time to navigate efficiently and find specific features.

What problems is the product solving and how is that benefiting you?

Jama Connect helps solve the problem of inconsistent requirements by centralizing all documentation, ensuring traceability, and improving collaboration across teams.

What do you like best about the product?

A valuable aspect of Jama is in its inherent traceability capabilities and its wide modularity. One can completely customise their item types and dictate the desired (and optional) traceability between those custom item types. Moreover, the automatic versioning of requirements and the ability to have enduring comments on requirements helps with a project/product that has been in a live environment for a number of years. This way, the exact meaning of requirements through its varying versions can always be validated. Although the layout of Jama takes some time to get accustomed to, the menus are very intuitive and it is usually clear how one should navigate the environments. We have not had the opportunity to integrate our Jama set with other often-used tooling in the industry, but the fact that Jama offers such integration capabilities is very useful for an organisation such as ours

What do you dislike about the product?

There are so minor complexities that one could bump into whilst trying to organise the Jama environment to your own needs and desires in spite of its modularity. These can be circumvented through different design choices, but could initially hamper creativity. For example, a requirement can only be attributed to one Release, whilst it was our wish to let it come back in several Releases as part of different requirements packages. Moreover, the lacking of a visual 'family tree-esque' traceability overview can make the structure a bit more difficult in larger projects

What problems is the product solving and how is that benefiting you?

Jama helps us by providing a platform to properly record and subsequently manage requirements of the business of our organisation and then translate those in technical requirements. The benefit of doing this process in a tool such as Jama is immensely valuable to retain insight into the previously captured information