When I add custom fields to a record (Ideas, for example), that reference another record (eg Releases), I had expected that doing so would link the records.
When I discovered this was not the case, I was disappointed as the workflow I had in mind will not work as intended. Because the custom field does not link records, the custom field is actually detrimental, as someone could select one Release in the custom field and select an entirely different linked Release, which would inevitably lead to confusion.
I don't understand the point of only having custom fields that merely "point to" other records, without also having the ability to have this field create a bi-directional link. A custom field that shows up prominently in a record is way better CX, especially for those not intimately familiar with the tool. Comparison:
Custom field that links to record |
Current Steps |
|
|
Hi there, thank you so much for sharing your feedback. I am going to merge this idea with the one you referenced above.
I am curious about the specific example you mentioned -- linking ideas to releases. Can you share a bit more about your use case and what you are ultimately needing to accomplish? Thanks!
see also https://big.ideas.aha.io/ideas/A-I-9055
Manually linking each Idea to Releases and Initiatives is so painful 😢