Just like Custom field values will transfer from ideas to Feature/Master Features/Initiatives when promoted assuming a custom field with the same Key name exists in both, the same should occur with many to many custom fields as well. My use case is as follows:
1 - I add a Customers custom table. I add it to both ideas and to features as a Many to many relationship type.
2 - I select a few customer values for an idea.
3- I promote the Idea to become a feature.
I expected/hoped that the customer values would populate the corresponding feature since the same table is being used in both. That did not happen. I would expect this to be a common use case associated with Promoting ideas.
Thank you for the idea. This is possible today by setting the same API key on the idea and feature custom fields. The status of this idea was out of date. You can learn more here: https://www.aha.io/support/roadmaps/strategic-roadmaps/ideas/custom-fields-from-ideas-to-other-record-types
We have various customers that utilize custom tables having the ability for those to be promoted to features.
+1
Would love this for one-to-many fields also
In our case, keeping the custom table linked to the same record, so that if a custom table value is updated at the feature level it is also updated at the idea level (and vice versa)