Skip to Main Content
Status Unlikely to implement
Categories Features
Created by Chris Humphreys
Created on Apr 29, 2016

Shared custom field options between Features and Ideas

We have a custom editable tag field on both Ideas and Features. It's great that the Idea field values come over automatically when the Idea is promoted to a Feature. It would be even better if the list of available tags automatically synced between the two fields. So, if we add a new tag to a Feature, that tag will be available in the Idea tag field as well (and vice versa).

  • ADMIN RESPONSE
    Apr 30, 2016

    Thank you for the request. As I'm sure you know, the current way to handle this would be to manually view/add this information by clicking on the Idea link (present on the Feature card).

    At this time, we are unlikely to make updates in this specific area. We can see potential issues around syncing between the two records (and that in some cases, many users might prefer the tags to be different between Ideas and Features). Including additional configuration settings around this would end up creating too much expense for a feature in this area. 

    Because of the reasons noted above (along with current capabilities), we are unlikely to make these updates. We hope you can understand.

  • Attach files
  • Nitin Julka
    Reply
    |
    Mar 27, 2017

    For us, we'd like a custom field in the feature (eg. link to spec) to be automatically visible on the idea once an idea has been promoted. 

    I'm surprised that Aha! is suggesting "double entry" for this use case.

    Sorry if I'm misunderstanding something.

5 MERGED

Option to link or share custom fields between Features and Ideas, so choices only have to be managed once

Merged
In APP-I-1989, there is a suggested workaround to promoting categories from Ideas to Features, which is to use Custom Fields instead (which in itself seems a bit odd). Anyway, I have gone along with the advice and have set up matching custom field...
Mike Knowles over 6 years ago in Ideas 0 Unlikely to implement