Aha! Roadmaps | Carry custom field values from requirements to features

Custom fields are used in Aha! Roadmaps to capture information that is important to your team and how they work. Usually, you apply custom fields to a custom record layout, apply that custom record layout to a workspace, and start gathering that critical data as people in your Aha! Roadmaps account start using your custom field.

However, some record types in Aha! Roadmaps can be promoted. If a requirement's scope of work expands, it can be promoted to a feature. A new record type means a new custom layout — so if you want to use a custom field in both layouts, you will need to make a few simple tweaks.

Carrying over custom fields upon promotion

Requirements are intentionally simple record types, intended to be components of a feature's work. Custom fields on a requirement allow you to track more sophisticated information. If you promote a requirement to a feature, you likely want that information to come along.

To do this, you need to add the same custom field to each record type's custom layout. You will need to be an administrator with customization permissions, and you can add the field by navigating to Settings ⚙️ Account Custom layouts.

• In the Requirements custom layout, note the Key of the custom field(s) you want to carry over to features. Do this by clicking the More options button beside the custom field, selecting Edit custom field. Then click Show advanced options and remember the value in the Key field.

• In the Features custom layout, create a custom field of the same type, and give it the same Key value. Add it to your custom features layout.

Custom field values (including note fields) will automatically carry over from requirements to features when the following criteria are met:

• Both fields are the same custom field type.

• Both fields have the identical API Key.

• Both fields are visible on their respective custom layouts.

• If the field you want to carry over is a predefined choice list or predefined tags field, both fields need to have the same predefined list of values. Any values that do not match will not be carried over.