Polymorphic relations. When creating relation, ability to have many Types from which to choose, and not just one Type

Thank you for the comment, it indeed describes the value well. Some comments from me:

  1. With blocks we gave this feature more priority, since there are things that can’t be done without polymorphic relations
  2. I seriously underestimated effort, it is much harder to do and it’s a significant technical challenge.
  3. I hope we’ll do a spike in the next months to see how hard it is to implement.

I wanted to just let you know that I moved my vote here over to the request here:

Right now I need that above request more than Polymorphic, but it’s hard for me to quantify to what degree having said that…

I would really like to also point out that I don’t understand the 5 vote limitation. In particular for many of us veterans of the forum, it would be nice to be able to vote on more posts. I think Team Fibery could give us some good faith that we won’t go voting willy nilly. I think it’s odd and artificial that I have to remove a vote here because I don’t have enough.

I’d also like to pose the question to @mdubakov around this point, and @Oshyan eager to get your 2 cents too, that do you guys limit feedback in your back channel to just 5 votes per user? So if a user writes in a request a 6th time, how would you figure out where to remove the vote? I’m asking because you’ve generously shared your backlog and votes around features in the past, often showing that requests you get directly from users have far more “weight” in votes - and that’s how you showed them, with actual numerical value - than requests here in the forum. I recall that Polymorphic barely showed up in the chart here:

yet it’s the top category now that we have votes.

Hope that’s useful. Would really like more votes, because without them I think we have a skewed view of requests. And would really like to know if you impose this limit on the “internal” tracking of users. Thanks!

1 Like

I don’t see anything about Polymorphism in the chart at all.

A post was merged into an existing topic: Feedback management problems + now you can vote for missing use cases here :mega:

I accidentally posted a reply here, when I meant to move it to a new thread. And although there is mention of it above, I wanted to just make a new reply here to make sure @B_Sp saw it was a reply to this topic. Will be more careful about which thread I am replying to in the future. :joy:

It is there at least on the “List” view:


Would love to get an update here guys.

My team has come up on this again as we build out new areas with multiple levels. We are building some multi-level structures in a software system. Basically, three apps, One has 4 levels, the other 3. There structures are in turn connected to a couple of types of Dev work items in other apps: We have multiple story types (Technical, User) and related tasks and bugs.

As we build it out, we are seeing that in some cases, structures don’t all have four levels. There are items on level three, or two even, that are the end of that particular “tree.” The stories need to link to the item that is being built, though. So without Polymorphic, in order to have the relation of a story to all levels I need, I have to have three Types in the hierarchy relate to the Story Type in the other App. This is getting very unwieldy. Or, I have to artificially create items in my structures down to the bottom level of each app, even though in reality this may not reflect how my structure looks.

This is basically a repeated instance of multiple examples I already posted in this thread, but just wanted to add yet another use case here.

Glad to see we’re up to 10 votes here, really hoping for some movement on this soon!


I don’t mean to be the primary torch holder of those of us really eager for this feature, but since it is about 1/2 year since @mdubakov weighed in here, would love to get another update on the team’s thoughts around this. I’m aware we have a good deal of visibility into what you are working on right now, such as blocks and new Entity View - both of which I eagerly anticipate. But my team still has a bunch of big things we want to do in Fibery, mainly around hierarchies we need to represent, that are blocked by the lack of Polymorhpic.

Would even be happy to hear if you guys think this might be addressed in the next 1/2 year, or not till 2023, etc.

In closing I’ll just add that if you can get this live, it will be one of Fibery’s truly differentiating features in the market and I think you guys should leverage it when completed to pick up some of the networked-thought folks flocking to Roam/Notion etc. as those tools have nothing like this. And I’m sure they don’t even have it thought through and on the dev radar yet, you guys have a leg up here!



I notice in the schema lots of fields related to “Mixins”. I assume that’s not something that could be leveraged for this purpose, or it would already have been done.

'fraid not, sorry.