Skip to Main Content
Status Future consideration
Categories Product
Created by Karie Kelly
Created on Jul 9, 2021

Associate the same custom field to more than one Aha record type

I've seen this mentioned a few places, but the Aha! staff seems to keep deferring to custom tables as being the answer, which isn't the need.

When I create a custom field - let's say the customer's name or the segment impacted - I want to add it to the Idea, Master Feature, and Feature layouts as I want to:

  • Minimize maintenance of the set of valid values

  • Carry forward when one type of record is promoted, merged, converted to another without losing the data

Today, I must add that one custom field to each record type (in the above, I must add to Idea, Master Feature, and Feature), use the same internal reference key, and maintain the values as they evolve.

Both the setup and maintenance would be more efficient and less prone to error and data loss if you can create a custom field and associate it to all relevant record types - similar to how Atlassian and IBM tools manage.

Behind the scenes, with minimal disruption to your UI, you could maintain the same structure - but, update the front-end to allow maintenance in one area to limit the impact.

  • Attach files
  • Paddy Corry
    Sep 23, 2022

    I use a pre-defined tag field on layouts to help identify dependencies. The same list is used across four different layouts at the moment, so this idea would really help.

  • Guest
    Mar 17, 2022

    It would be really helpful if custom fields were global. We're capturing a lot of financial details and other custom fields on the idea record which I then have to recreate on other Aha records. Some of the custom fields are worksheets with calculations. And if one worksheet has to be modified, I then have to modify it on 2-3 other records. This is time-consuming and cumbersome to maintain.

  • Ronit Binshtok
    Feb 17, 2022

    It simply will save maintenance time since in several cases, I need same custom field to appear in more than one record and currently I need to update in multiple places each change.

  • Guest
    Dec 9, 2021

    This would be very helpful as we have custom fields that appear on multiple record types. A custom field should be global so it can be applied to multiple records and not have to be created multiple times.

  • Guest
    Aug 4, 2021

    This seems like an obvious need. We have a similar issue with a need to capture client names associated with ideas, epics and features. Each time a new client is added we have to manually update 3 different pick lists to make sure we keep them in synch. Custom tables will not work since you can't link the custom table to Jira.

    If I could vote this up 10 times I would do so.

  • +1