🔴 STOP Relationship Fields From Breaking Across Lists
A
Adrián
When you create a Relationship Custom Field and add a task to another List, the task loses its custom relationship field.
For example, in Sprints, we have a Backlog with all tasks grouped by Product (Product comes from the Product Roadmap list) using a Relationship List. When we add a task from the Backlog to the Sprint Folder, the task no longer stays connected to its Product.
We need Relationship Custom Field values be available and stay the same when a task is added to another List as other custom fields do.
Log In
I
Ian Lopez Zamora
I totally agree with Adrián. This is not a minor detail: if the relationship fields are lost when moving or adding a task to another list, the traceability of the work is directly broken.
In our case, these relationships are not “decorative”; they are a key part of the flow: product, planning, sprint, dependencies and monitoring. The fact that a task loses that connection when it is transferred to another list forces us to review and rebuild information manually, with the risk of errors and waste of time.
We need custom relationship fields to behave the same as other custom fields: to keep their value when adding the task to another list or folder. Right now, this greatly limits the actual use of relationships in workflows with sprints, backlogs and planning by product.
Please give it priority or at least a clear answer as to whether it is contemplated to correct it.