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?

Traceability is made easy when you have a simple structure

What do you dislike about the product?

difficult to adapt to complex structures
we need to use it for several projects in parallel and implementing our current structure in Jama is resulting quite complex and time challenging

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

we have been managing requirements in several excel files, where it is difficult to have the big picture and the review process is slow and crumbersome. the occasional human errors are not detected by excel. Jama is allowing to show immediate traceability parent/son and makes it easier to detect changes and address conflicts.

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

What do you like best about the product?

Particularly convincing is the intuitive interface and the efficient traceability function, which greatly simplifies linking and tracking requirements.

What do you dislike about the product?

The admin functions are not very intuitive and often require some time to get used to.

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

Until now, the traceability of requirements was very difficult or even impossible. Jama solves this problem 100%.

What do you like best about the product?

Jama is easy to access from anywhere, it does not need any additional software to be installed.
has very powerful features for documentation and traceability, great visualization and tons of existing template types to suit the specific project needs.
multiple users can work simultaneously; this is great for large organizations.

What do you dislike about the product?

exporting to word using a specific template a bit of a hassle, need some expertise in velocity to do this.
otherwise, the word template is the best bet. however, some additional documentation should fix this issue, I think.
for test runs feature, it might be a good option to enable relationships to test cases.

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

end to end traceability with great analysis tool along with rest api interface for test automation, this is a game changer for automation.

What do you like best about the product?

The best feature in JAMA is the requirement review.
Modern and easy to user UI

What do you dislike about the product?

Licensing Behavior Is Problematic
The most critical issue with JAMA is how it handles floating licenses. When a Creator license is unavailable, the user is automatically downgraded to a Reviewer role. Unfortunately, a Reviewer can only access requirements that are actively included in a review—meaning they are effectively locked out of the full set of requirements. This restriction is highly problematic, especially when we're attempting to align our workflow and documentation practices around JAMA. We expected that a Creator without an available license would be downgraded to a read-only role, rather than losing access to essential content.

Difficulties Managing Multiple Products
JAMA works reasonably well when focusing on a single product. However, managing multiple products simultaneously becomes overly complex. The system does not provide an intuitive or visual way to differentiate or compare between products. For example, there is no visual overview of differences or changes across product versions, making it hard to track progress or ensure consistency.

Limited Visibility into Requirement/Test Status
Another major pain point is the difficulty in retrieving the status of only a subset of requirements or tests. JAMA lacks flexible filtering or dashboard views that would make it easier to focus on a specific area or segment of the project. This limits our ability to efficiently monitor progress or identify issues.

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

Ensuring that our company covers all requirements with test before releasing.
JAMA also needs to support us in ensuring that we tests on different levels and not only tests on system level.
Finally JAMA has to helps us provide products requirements.

What do you like best about the product?

jama is a versatile tool designed to support the creation, maintenance, and review of requirements in day-to-day operations. It streamlines the process of connecting requirements and enables effective traceability. Additionally, jama can be customised by adding specific attributes to meet your unique needs.
The tool is user-friendly and straightforward to operate. Most individuals quickly gain confidence in its use.

What do you dislike about the product?

The traceability dashboard could be enhanced by incorporating clear coverage metrics, both in percentages and absolute numbers, based on the defined relationships between item types. Established tools such as ReqTracer and Reqtify offer visual dashboards that display the status of traceability. Implementing a similar solution would be beneficial.

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

Jama enables management of multiple projects and connects them to extend traceability between projects. Requirements can be inherited, making it easier to manage product variants. Additionally, all projects in Jama can follow the same process, supporting collaboration across teams and projects.