RELATED IDEAS
Merged idea
This idea has been merged into another idea.
To comment or vote on this idea, please visit A-I-11109 Associate the same custom field to more than one Aha record type.
Re-use custom fields in any item type
Merged
It's cumbersome to need a unique custom field for the same data across different item types. It would be more efficient to be able to use a single custom field in multiple item types.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +2
8
MERGED
Ability to create/maintain a custom field across multiple Aha records types
When you have the same custom fields across multiple Aha record types, we are required to input the same information multiple times.
When you have a change to the custom field, then you are required to update that custom field in multiple Aha re...
0
Future consideration
10
MERGED
Ability to move or copy custom fields between different categories
I would like the ability to move or duplicate custom fields from one category to another (eg. from Features to Initiatives). For moving, of course you would need to disassociate it from all layouts. I have a customer that requested many custom fie...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved
I am new to Aha! and finding it more time consuming setting up the initial layouts. Though Epics, Features and Stories have different purposes, there are similarities used though at a deeper level. It would be nice to be able to be able to link a custom epic layout or field to a custome feature layout/field. Thank you for your consideration.
You can use custom tables to maintain a single list of values and use that custom table across multiple objects, however there are some limitations when using custom tables so make sure you check them before going down that path.
It would definitely be useful to have the option of using a single custom pick list field across multiple objects.
Same. We do annual planning and set up quarterly OKRs that track back to those. I need a way to then draw that line down a level further to releases to demonstrate how everything we are releasing rolls up to quarterly and annual goals.
Strongly support this; other use case is when you want to adopt a custom scoring matrix or worksheet that can be used across features, master features or even initiatives. These take time to build and it would be great to have the ability at least to copy an existing custom field from another Aha! object. Thanks
Us too. We have internal partners that specific goals, initiative, releases, features are targeted.
we have the exact same use case
For a use case, we have a droplist that contains a list of clients. That list is rather long and we have the same client list for ideas, features and releases. When a new client is added, we have to add the client to each droplist. Currently, we have a note that contains the list, we add the new client, then edit each droplist. This manual effort is prone to error.