What if entity view was treated as a dashboard?

1

I remember it was recommended to use docs as dashboards, but what if the entity view was the dashboard?
At the end of the day, each project will need a dashboard to see open tasks, amount of time spent, etc. Each project is already an entity! Why not each entity is a dashboard? We can already add the data as fields (not all but most). This means also adding embedded views as relasion fields I think, as well as reports. It would be to be rethought a little bit, but I think it would be much more scaleable as a dashboard system than using docs (or rtf) as dashboards.

2 Likes
2

This would be my dream scenario.

1 Like
3

Imagine I add a rich text field to the Project db (called Dashboard) and therein I write stuff, create an embedded (relation) board view of tasks, add an embedded list of assignees, have a burndown report etc.

How does what you are asking for differ?

Perhaps you need to embed single field values?
Perhaps you expect the ‘dashboard’ content and layout to be replicated for all Projects?

4

Do you mean in a RTF or as a multi relation in the entity?

Edit: as sorry I just reread. The difference is 1. yes, having it the same accross projects, and also the single field as well, all of the above really hahah. Adding a large lookup/formula in the center. Like a dashboard style. I can find some examples and edit this in an hour.

5

This is kind of what I meant:

image
image1594×942 33 KB

It’s 3 column layout with 3 different embedded views.

1 Like
6

I see, makes sense. Yeah the problems with this are like you outlined:

  1. Each project will need to have a dashboard set up manually (or a duplicate template that wont be editable globally if I want to make changes after the fact)
  2. Cant put fields on the canvas. (there was feature requests for this to be added to RTF but I can’t seem to find it right now)
  3. Much harder to make responsive on mobile, (i think)
  4. It looks really, really bad. I’m sorry.

My suggestion is for an improved entity view, specifically with the mindset of it being a dashboard. 3 options for views: 1 col, 2 col, and freehand (or dashboard) style entity view. Where you can move views, lookups, linked reports (which isn’t a thing yet i think), around on a grid. Then each person has their own personal dashboard in their own user entity. (Which would then be the home page)

Some examples of dashboards:

This is from Target Process.

Screenshot 2025-02-26 at 16.31.35
Screenshot 2025-02-26 at 16.31.351742×992 162 KB

From Directus, dashboard. (I highly suggest you guys play around a bit with directus)

image
image2880×1750 412 KB

Scoro Helpdesk

image
image1920×1532 178 KB

I mean just Google image search “Dashboard” and I think you’ll see the difference…

I added this because even though there are other requests to add dashboards, I think embeding them as an entity view makes the most sense.

1 Like
7

Yep. I assumed this was core to the use case you have in mind.

Yep, me neither.

Part of a bigger problem I suppose :grimacing:

No doubt that this is (theoretically) easier to fix than the other three :wink:

1 Like
8

Funny I was just looking at what’s going on with TargetProcess yesterday as some of those views were just fantastic, and obviously we have that pedigree here in Fibery! I hadn’t looked that them in maybe a few years and there is still some stuff, like the more sophisticated Kansan boards, that we just don’t have in Fibery. I quoted one of those here:

Suggestion for App Dashboard / Hierarchy View from left Menu

Good to see you also show how good these were, would love to see Fibery continue to develop towards achieving views that were as good as TP!

9

can I have some examples of an dasboard like this as an Project entity