RELATED IDEAS
Sync custom fields with standard fields when idea is promoted
We have a custom field for goals in the Idea ticket (where the requester must select which strategic goal their request ties to), but we can't map this field to the Goals field at the Feature level because they are both not custom fields.
We have this issue with a few other fields as well including the Brands field - which is used as the 'categories' field in the idea, but a custom field in the feature. Note, for this specifically - the reason we are using the categories field to indicate the brand is so that we can filter by brand on the ideas portal. As such, I have voted for this ticket since that was a workaround https://big.ideas.aha.io/ideas/APP-I-1471.
-
ADMIN RESPONSEAug 29, 2024
Now there is a new "idea categories" custom field type. Add this field to your layout for features, epics, and more. Then, when you promote an idea, the idea's category will be copied to the feature automatically.
We will leave this idea open to track the need to copy other types of standard and custom fields.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
5
MERGED
Allow Idea submitter name to populate onto the feature.
As a product manager I want the name of the idea submitter to populate into the feature when an Idea is promoted so that design or engineering can follow up with questions. Use case: We use an Ideas portal to allow internal team members to submit ...
0
Future consideration
22
MERGED
Initiatives custom field should promote with Ideas
We created a custom field to track initiative on an Idea. It would be great if the value in that field would promote to the initiative field on the feature when we promote the idea to a feature so that we can maintain the mapping to strategy.
3
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved
+1 for this specific to Personas and their links to Features / Master Features / Initiatives and vice-versa.
I want the ability to select a persona for each feature (which I can do via a custom field), but when I go back to view that Persona, even if i add Features as a custom field there, I don't automatically get the features where I chose that Persona. So the custom fields become custom list-of-values fields, but there is no established actual relationship; it's just a display convention. I want the selection of Persona from a Feature (or Master Feature or Initiative) to be an actual relationship that I can see in both directions.
I can "hack" around this by running a report against my feature list grouping by / sorting by personas, but that's not a great solution.
This would be very useful so we do not duplicate the effort! One the main reasons we are using AHA is brecaus of the goals!
Can this also be true for the reverse as well? In essence create a custom field and have it map to a standard field.
Similar need - We have a custom field in Jira used to track story points, i'd like to map that to the Estimates field.