Would be great to have an option to enable a Code View for anywhere the text editor appears throughout the app. I understand not everyone would want this, but if it could be an option where the user could elect to have a Live View tab and a Code t...
Guest
about 8 years ago
in Account settings
0
Unlikely to implement
Disabling anything to do with Time logged for 'reviewer/viewer' access levels
We have a requirement where we are using Aha for our time entry and ultimately invoicing. However currently if we share it with our clients, they can see any/all time entered immediately before PM's have had a chance to review time and determine i...
Guest
over 8 years ago
in Account settings
0
Unlikely to implement
Our teams are using tags heavily to add planning metadata to features. Over time, duplicate and mistyped tags are introduced which can cause confusion. At the moment, only those with admin access (one person within our organization) can clean up a...
Gordon Cloke
over 6 years ago
in Account settings
0
Unlikely to implement
We should be able to configure specific release statuses so that they're restricted, editable only by certain users or user groups.
We have a Program Management group which maintains an authoritative list of releases the product organization has c...
Guest
over 8 years ago
in Account settings
1
Unlikely to implement
We recently instituted SSO on our Aha account, but currenlty have a couple of dozens folks who have the typical username/PW login profile active. I'd like to make a universal/batch change to force all users to log in via SSO, however there is no c...
Joe Carpenter
over 9 years ago
in Account settings
4
Unlikely to implement
Extend product tree to support different configurations of a product line
I manage a product line where each product has different configurations. Currently I get around it by making different releases, but it really doesn't solve the problem because the different configurations have different requirements. So, being ab...
David Spada
over 9 years ago
in Account settings
1
Unlikely to implement
In workflows, add the ability to limit setting a certain status to certain users.
In workflows, most of the time a status like "approved" is available. However, at the moment everybody can set this status, so it pretty useless.
If only certain users (e.g. with a certain role) could set the status to approved it suddenly gets v...
Guest
over 9 years ago
in Account settings
2
Unlikely to implement
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
over 7 years ago
in Account settings
0
Unlikely to 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
over 7 years ago
in Account settings
0
Unlikely to implement
Add REST API to modify paid seats and simplify account provisioning
I do create reviewer and product owner users in aha.io automatically via the REST API. If I create a product owner and this exceeds the current available paid seats I get an exception.
It should be possible to read the amount of available paid sea...