If a parent and child entity have the same relational field for example: Stories and Subtasks both have a relation to Products. Then when creating Subtasks on a Story card - how do I automatically assign the same Product to the Subtasks that are selected on the Story. Now when creating Subtasks, the…

It sounds as though Subtasks should use a lookup to inherit the Product from the Story, rather than having a direct relation field to the Product.

Thanks @Chr1sG . Could you explain how we should make this choice (between a relation and a lookup), in general?

You can use Lookup field in a Subtask and get project from Story, but only if the Subtask ALWAYS has Story. If Subtask can live without Story, then lookup will not work. However, we are working on automations and for such scenarios it will be possible to create a rule to set Product automatically f…

Can the Lookup capability become more complex? [image] CHANGELOG: October 1 / Create Documents and Whiteboards inside entities, Automatically link entities based on rules Changelog Can we not do this with a Formula field? Not just at a entity creation time, but always “li…

As a general rule (for me anyway) a relation should exist when it is meaningful for the entities to be directly connected. Lookups are about inheriting or inferring information from an existing relation (and is therefore read-only). So for a simple example, the classic hierarchy of Product → Epic →…

That makes sense. So how do I configure a sprint planning board with sprints as columns and projects as rows - that includes userStories grouped on project according to it´s “feautre product lookup”?

It depends on how your types are currently related. Assuming that you have a hierarchy of Project → Feature → User stories and you also have Sprint → User stories [image] then you could try it like this: [image] [image] Here’s the app: [image] Fibery | Start for free, upgrade when yo…

I have features in a separate app with a relation to userStories. Otherwise I have the same setup. The issue with this is that userStories that are not assigned to a project (only looked up by it’s parent) are not grouped with the associated project. Hence the need to automatically assign UserStori…

[image] Jim_Larsson: Or is there a way to group rows by lookup reference? Yes. You can use lookups as the row grouping (or column grouping for that matter) in just the same way as is possible with relations.

That makes sense. So how do I configure a sprint planning board with sprints as columns and projects as rows - that includes userStories grouped on project according to it´s “feautre product lookup”?

How to assign relations to child entity on creation?

Get Help

Matt_Blais March 28, 2021, 6:25pm 5

Can the Lookup capability become more complex?

Topic		Replies	Views
CHANGELOG: October 1 / Create Documents and Whiteboards inside entities, Automatically link entities based on rules Changelog	31	4595	March 28, 2021
Entity list view: Filter view Get Help	16	615	February 20, 2023
🦜 April 2, 2026 / Show Fields from relation without Lookup, AI Integration Agent Changelog	47	630	June 3, 2026
[DONE] Request: 🔀 Sort Related Entities within Parent Entity View Ideas & Features	16	2100	September 9, 2022
Fibery Product Workspace Fibery Showcase	6	2278	April 2, 2021

How to assign relations to child entity on creation?

Related topics