Guide
Multiple Entity Views allow users to create and manage multiple layouts for any database entity.
What problems does it solve?
Sometimes a database can be large with dozens or even hundreds of fields, and different users in different contexts might want to work with only a subset of these fields. Here are a few examples:
A Feature can look different from the QA perspective than from the PdM perspective.
As a project manager, sometimes I want to work on project finances, but later switch to project scheduling.
Multiple Entity Views allow to switch context with two clicks:
How to set up Multiple Entities Views?
Enable Multiple Views through the "Manage Fields & Layout" control.
The switcher appears once Multiple Views are enabled. Click on Add view and add more views here:
What else you can do:
You can add, rename, duplicate, and delete entity views
Views are listed in the switcher and can be reordered as well
Fields can be added or removed from any number of views
Different entity views can have different layouts
Multiple Entity Views will be preserved in Share Space as a Template
Pin Entity Views
You can pin several Entity Views and enjoy quick navigation between these Views. For example, you can customize them for specific use cases and switch focus fast.
Open Entity Views drop down, click … for any Entity View and select Pin action. This is how several pinned Entity Views look:
Rules to specify which Entity View to open based on some field value
You can set rules that open a specific, pre-configured Entity View based on a field’s value (like Project Type, Feature State, Task relation) or logged user fields values (like Role, Team). It’s a simple way to show the most relevant information to users when they open an entity from any place.
Rules to specify which Entity View to open based on some field value is a Pro plan feature
Here are few use cases that you may find useful:
Different project types. Open a tailored view for Integration, Service, or Maintenance projects—each with its own fields and relations.
Tasks that change context. Show different information when a task belongs to different projects or teams.
Accounts by type. Show a focused set of fields for Client, Vendor, or Partner accounts.
QA focus during testing. Auto-open a “QA” Entity View when a Feature moves to In Testing to show bugs and test notes on top.
User Role or Job Function. Show QA view by default for a user in QA role.
User Team. Show QA view by default if a user in QA team.
Click on … near some Entity View and select Set up Rule action. Then specify the rule for this Entity View and Save the rule.
Rules execution order is defined by Entity Views order. For example, in the image above Release Day view will have higher priority than QA view.
You can also edit and delete entity view rules easily.
Rules to hide Entity View
You can also hide specific Entity Views based on rules. This allows you to control which views are visible depending on logged user fields values or entity fields values.
In many setups, the same entity is used by different teams and across different workflow stages. Over time this leads to problems like: too many tabs on an entity, Views that are irrelevant for certain roles, Views that only make sense in specific workflow stages. With Hide View rules, you can automatically remove views when they are not relevant.
Some use cases:
Role-based visibility. Different teams may need different interfaces for the same entity.
Workflow stage-specific views. Some views only make sense at certain stages of work.
Different entity types in one database. When a database stores multiple types of work (for example Projects and Service Calls), some views may only apply to one type.
To enable Hide Entity View rules, click Views on entity view → … near view name → Set up rules.
Q&A
What happens if I add new field?
When a field is created from some Entity View, it is visible in this Entity View only by default and it is hidden from other views. Note that if you add a new field from Database, it is still added to all Entity Views.
What entity views are displayed for entities shared to web?
Currently, only the first (default) Entity View is visible for publicly shared entities. If you'd like to configure which Views to show in this case, please reach out to us and describe your use case.