The user stories listed out are pretty generic, but it could potentially provide that. However, I don’t know if that view is the best for non-power users. It also doesn’t give you access to non-destructive browsing, which i mean as that you can filter entities without impacting a current view that exists. Basically what I’m describing is that a typical user is simply going to want to jump and view all entities of a particular type, then filter them down further.
For example, think about a new team member that is like, “I wonder if we have a Topic type defined.” If they go to app map, that isn’t going to help them view entities for the Topic type. They could only see the definition of what the Topic type is and potentially modify that. Instead, they could search for “topic” and they’d see what I think is the only true simple directory of types on the right. If there happens to be a view with the same name as the type, they would discover it via search. Otherwise, there is no way to go view entities of that type quickly. Even if they do get to a view, then unless they have some kind of read-only permissions they’d be modifying that view or they’d have to duplicate it and remember to delete it if they want to explore them further.
If I understand correctly, I thought the desire was to see the type in search as a result, which when clicked on would take you to go view entities of that type. Right now it shows up, but is only used to select which type you want to create.
Well, both really. With some clever design work, this view to filter all entities would have a “Type” filter, which would contain the potential types to filter on. The filter could serve double duty in also being a list of the types. The search functionality pretty much has that simple directory of the types, but it is focused on entity creation, instead of filtering and would need an expanded advanced view to add more filtering options.
Yes, sorry, the same filtering. It could potentially be viewed as an advanced search. Or, there could be an “Explore” area called out in the left nav.
Yep. For the reference, you could think about the types as an entity of the Type class. In other words, each Type (Task, Story, Epic, etc) are an entity of the Type class. If you could have a details view for a specific Type, in the same way we have that for a specific Task, it could show relationships such as “Documents”, “Views”, “Entities”, etc.