Allow an idea portal to be linked to another system so that users of the other system were automatically authenticated to the ideas portal without the need to separately register or log in.
Like many other users, we map features to tasks and requirements as sub-tasks in our integration. For us it logically makes sense that JIRA Epics are therefore bound to releases (as tasks sit under Epics, and features sit under releases) - we use ...
Allow customization of billing admins listed when user has no seat allocated
When a user who does not have any product permissions tries to sign into Aha! they are presented with a warning alerting them to contact a billing admin to get permissions. This warning is a list of all users with Billing Admin permissions. For te...
Allow user to set a default release when promoting ideas to features
For my particular workflow, I would like promoted Ideas to default to the first parking lot column. Today, they default to the first release in the list. Ideally, the user would be able to set which release is the default when promoting Ideas (or ...
Matthew Monahan
over 5 years ago
in Ideas
2
Shipped
The new research tab in the Feature needs to include idea #
Ideas were recently moved from the related tab to a new research tab. The new research tab (or lightbulb icon) within the feature shows the idea name but not the idea reference number which is what we use for a range of visibility/communications w...
Adding Features in Feature Board - Auto add to Release view
Whenever we add a feature to a release from the "Features Board", clicking the three dots on the release it does not seem to truly add it to the release. The edit area doesn't show the Start On and Due On dates, and when we go to the Release overv...
Steve Podzamsky
about 6 years ago
in Features
2
Shipped
Please add in additional options for visibility in portals. There are currently two options, Default or all ideas come in under a specific selection. I would like to be able to decide how an idea acts in a portal for an Aha! user, Employee, and Po...
Sometimes ideas are small and specific, sometimes they are big (ex. add a button vs. create an app that does x). Currently an idea is assumed to only be for a feature.
After merging three ideas with several votes against each into one master idea, the votes on the master idea are now at 0. Instead, it should be a total of the votes from all the merged ideas, since it's lost it's "popular" status.
We are getting ready to share Aha with key stakeholders around the company, and we do not want to share the inside engineering chatter with the rest of the company. We have comments in JIRA that should not be broadly available. I would like to be ...
Cameron O'Rourke
about 9 years ago
in Jira
4
Shipped