How to Create Document Views Using Filters

Published Date: July 3, 2026
Validated: Yes
Audience: Everyone
Products and Versions Covered:

Jama Connect® version(s)
- Cloud/CVC
- Self-hosted

Summary

Filters can be used to create custom document views. For example, you can combine a project glossary with a set of requirements so that the glossary appears at the beginning of reviews or document exports—without duplicating items in the project tree.

Resolution

Example: Add a Glossary to the Start of a Document Export

To create a single glossary of terms that appears at the beginning of reviews and/or document exports:

Create a new filter and give it a name (for example, “Document View”).
Select the project.
Add a rule to include all item types where Location is under Glossary.
Add a second rule to include all item types where Location is under System Requirements.
Set “Limit to items updated within” to All dates, unless you want to narrow the results.
Define the sort order (for example, Heading – Ascending).

Applying this filter produces a document view that lists glossary terms first, followed by system requirements.

This filter view can also be:

Sent to a Review

Applied in the Explorer tree

Use Cases: Pros and Cons

Use Case	Creating Document Views with Filters	Structure Explorer Tree to Resemble Document Structure
Add a glossary to the beginning of the document exports for different documents	Pros: No need to duplicate glossary items in folders. Cons: Users must apply the filter to view the document structure.	Cons: Duplicated glossary items must be kept synchronized across the project.
Include the project glossary in reviews of different project components or sets	Pros: Reuse a single glossary without duplicating items.	Pros: Reviews can be sent directly without applying a filter. Cons: Requires duplicating and maintaining glossary items across multiple document structures.

Use Case

Creating Document Views with Filters

Structure Explorer Tree to Resemble Document Structure

Add a glossary to the beginning of the document exports for different documents

Pros: No need to duplicate glossary items in folders.

Cons: Users must apply the filter to view the document structure.

Cons: Duplicated glossary items must be kept synchronized across the project.

Include the project glossary in reviews of different project components or sets

Pros: Reuse a single glossary without duplicating items.

Pros: Reviews can be sent directly without applying a filter.

Cons: Requires duplicating and maintaining glossary items across multiple document structures.

Key Takeaway

Filters provide a flexible way to create dynamic document views—such as placing a glossary at the start of exports—without duplicating content, but they require users to actively apply and maintain the filter configuration.

Additional Resources

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.

Related to