RELATED IDEAS
Synchronize additional fields when promoting an idea to an existing feature
Handling of duplicate ideas has been a very tricky thing. The way we solve this is by promoting multiple ideas to the same feature, making the feature a kind of 'control point' where all of the ideas come together.
The problem is that this introduces a lot of manual labour to keep fields in the feature up to date against the fields in the idea - namely tags and custom fields that we use (customer asking is the biggest one)
Ideal flow:
Select a set of fields in the idea that map to fields in the feature
whenever a new idea is promoted to an existing feature, this subset of fields would be added to the fields in the feature
Another option:
Create an automation that is triggered by 'when an idea is promoted to a feature'
Add values from field X in the idea to field Y in the feature
This would reduce a HUGE amount of manual work that currently goes into keeping these fields up to date
Echoing the need for this functionality - when we promote an idea to an existing roadmap object, it'd be helpful to be able to pass along field values, similar to how promoting to a new roadmap object works. Otherwise, the information transfer is very manual and time-consuming.
We are having a similar issue. When we promote an idea to a feature, we want a custom field on the idea to take on the feature's field value. For example - once an idea is promoted to a feature, I want the seasonal release of the feature to be reflected on the idea.
I thought this would be possible by creating a custom field on the idea that has the same API Key name as the feature's custom field, but I was told that we would need to create automation rules in each workspace to make that happen. That would result in hundreds of automation rules that we would have to maintain and keep up-to-date.