RELATED IDEAS
Allow to define the scope of tags/choice list custom field values (account vs. workspace)
It should be possible to define whether the values of choice list and tags custom fields (predefined or editable) are shared at account level (current behavior) or limited to workspace level such that workspaces can share a configuration but have their own pick list values. This is currently already possible for Aha! record relationships custom fields where you can choose 'Filter field values to <account/product line/workspace>', the same would be very useful for other custom field types.
9
MERGED
Adding values for custom fields at product level, not just account level
We have a number of Product Managers. It will be good if they are able to add values to certain custom fields so that an integration between JIRA and Aha doesn't break.
For example, components. If an engineer adds a component in JIRA, it will be g...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved
Different teams/workspaces in my organization would like to choose from different choice lists for the same custom field.
Currently I need to create a new custom field and a new custom layout to accommodate this request.
If I could configure the choicelist for a custom field at the workspace level, I could use the same custom field and custom layout.
That would make it loveable.
There are multiple product managers that oversee various products that use Aha. The tags that are created for one product, more often than not, are not relevant to another product. Right now, there are more than 100 tags in total when I only want to use around 12 Tags for the products I oversee. It's cumbersome to sort through a list that long. It would be nice to create tags and associate them to a Workspace so that I am sorting through a shorter list that is relevant to the product I am managing.