Author: Jakob Khazanovich
Date: June 16, 2025
Audience: Everyone
Environmental details: All Jama Connect Instances
Summary
This article explains the differences between saved view types in Jama Connect—Saved Trace Views, Saved Coverage Explorer Views, saved Live Trace Explorer Views, and saved Filters. It outlines which views are user-specific, project-specific, or shared across users, and clarifies visibility, editing rights, and best practices for managing views effectively across projects.
Solution
| View Type | User Specific? | Project Specific? | Instance Wide? | Visibility | Ownership/Editing | Notes |
|---|---|---|---|---|---|---|
| Saved Trace Views | ✅ Yes | ✅ Yes | ❌ No | Only visible to the user who created them. Can share with others using the URL. | Each user must create their own view | Saved views are tied to the project where they were created. Selecting them in other projects redirects you. |
| Saved Coverage Explorer Views | ❌ No | ✅ Yes | ❌ No | Visible to all users in the project | Only the creator can rename or delete | Best practice: have an admin create all coverage views. Must be recreated in each project. |
| Saved Live Trace Explorer (LTE) Diagrams | ❌ No | ✅ Yes | ❌ No | Can see saved diagram views. | Admins can save diagrams that other users can view. | Requires Creator or Creator (Float) license to see LTE. |
| Saved Filters | Optional | ✅ Yes | ❌ No | Can see filters created by other users if they select the option to make public. Can share non-public filters with others using the URL. | Only Admins can edit others' filters | Must have creator license and write permissions to create filters. Filters shared with the project are included in project duplications. Cannot copy/paste filters between projects otherwise. |
| Saved Sync Diff Views | Optional | ✅ Yes | ❌ No | Can see diff views created by other users if they select the option to make this view public. | Only Admins can edit others' diff views | Creators and Stakeholders can save diff views. |
References
Please feel free to leave feedback in the comments below.
Comments
0 comments
Please sign in to leave a comment.