Provide help with consequences of merging custom fields
The Aha! KB article on merging and converting custom fields explains that there are implications for integrations and reports when merging fields. Specifically: If an integration included the old custom field, you will need to update the field map...
Steve Dagless
over 2 years ago
in Account settings
0
Future consideration
Clarify the use of the term "allocate seat", as it's not clear a seat can be unpaid. :-)
Hi, I had a human-error issue where I had two users in my user list that I couldn't figure out how to give them view access. I clicked the viewer access button, but nothing would happen. It turns out it was because I wasn't clicking "allocate seat...
Guest
almost 8 years ago
in Account settings
0
Will not implement
Prevent non-billing admin workspace owners from adding paid seats outside their owned paid seat groups
The cure was determined to be worse than the ailment. Moved to an idea, tracked here: https://big.ideas.aha.io/ideas/A-I-13997 Currently there is an edge case where project owners are able to add users that take up paid seats outside the paid seat...
Chris Zempel
over 2 years ago
in Account settings
0
Will not implement
Number of functionalities in Main Menu contain different types of views we can use. However, not all these views might be useful or updated and it would be great to have the option to choose what views we use and we don't and hide the unused ones ...
When you login in from the aha.io page it spawns a new browser page. Stop this behavior and log me in from the current tab. I did not ask for a new tab to open and this ends to an endless number of useless tabs being opened. Please change how this...
Guest
over 2 years ago
in Account settings
0
Future consideration
Provide sorting capability for custom fields (tags and Choice lists)
We have a large client list and when a feature has been requested by a client, we associate the client to the feature. With a long list of clients, being able to sort the Alphabetically (ascending/descending) would make choosing the Clients far ea...
Jerrold Emery
about 8 years ago
in Account settings
1
Already exists
Alternate hierarchy to manage work through different lens
We look at the same Initiatives through two lenses: (1) the product lens, which Aha! solves really well; and (2) the program lens, which Aha! does not solve for.
The idea is to have an Alternate Hierarchy in Aha!, such that the same initiative c...
Guest
about 8 years ago
in Account settings
0
Unlikely to implement
As an Aha! administrator, I would like to control who sees banners from Aha! so that they don't blow past my banners thinking they are things from Aha! that they don't really need to read. I've learned from several of my users that they are not re...
Tom Beck
about 8 years ago
in Account settings
0
Will not implement
We have our company set up on the root-level in Aha with the product lines underneath this. For global visibility, we would like to give our marketing team the ability to add competitors to the very top company level, which then propagates down to...
Pieter van Aarde
about 8 years ago
in Account settings
0
Unlikely to implement
Status Categories are currently very specific to the creation of code/features, but not at all focussed on the strategic planning, evaluation, proposal, business case and executive approval phases of new features/ideas.
I would like to be able to ...