PINNED
Chrome extension to capture feedback from anywhere
What is the challenge? We work in many applications and Aha! can not build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? This res...
The first_name and last_name claims required by Aha! are not OIDC conformant, leading to duplicate information in previously conformant JWT tokens. This increases the size of tokens. This can also make it harder to use a common token for Aha! and ...
Guest
over 5 years ago
in User management
2
Unlikely to implement
I love the fact that we can now use the bulk import to import to-do's but these can only be applied as a one off to a parent record. It would be even better if we could use the bulk import to create a new 'release template' and equally export a re...
Sophie Ramsden
about 4 years ago
in To-dos
1
Future consideration
Engineering managers & team leads sit "in between" Aha! Roadmaps and Aha! Develop. They more than just team owner permissions, but not full workspace contributor permissions. Key use cases Team leads can provide initial estimates on features b...
Hi - as we're getting setup with Aha!, it would be great to have a forum where other Aha! users can share their insight and best practices. For example, how have others used tags and categories to delineate, report on, or prioritize ideas and then...
Guest
over 10 years ago
in Application
3
Future consideration
Allow for a cutoff timeframe to be specified for the Later column in Now, Next, Later
What is the challenge? PdMs have features planned for internal purposes out further than what we want the Now, Next, Later to show to internal business partners and customers. Because the later column is open ended "Future" it shows way more than ...
Guest
10 months ago
in Roadmaps
0
Future consideration
Removing the link between an Aha Feature and a Jira Epic should clear all fields included in the sync.
What is the challenge? When a Feature in Aha! is unlinked from its corresponding Epic in Jira, fields that were previously synced—such as the Aha! URL—remain populated in Jira. This creates a false impression that the records are still connected a...
Brittani Carmandi-Weber
10 months ago
in Integrations
0
Future consideration
What is the challenge? There are so many nuances to using Aha; the way items must be linked; certain fields are exposed when others are used. Aha is an increasingly complex software for us to use on a daily basis - and my colleagues and I find our...
Guest
10 months ago
in Application
0
Future consideration
Relating Features to Initiatives vs. Adding Features to Initiatives
What is the challenge? There are two ways a user can associate a feature to an initiative - but only one way officially links them. I am building various quarterly reports that display all features associated with an initiative. I went to each fea...
Guest
10 months ago
in Reports
0
Future consideration
What is the challenge? Feature available at Feature level is not available at Master Feature level What is the impact? time consuming to search for items Describe your idea Allow Name Search at Master Feature (Epic) Level
Alex Berestenko
over 1 year ago
in Reports
0
Already exists
Allow the use of "Integration" fields in Report calculated field formulas
Currently, integration fields like "Rally formatted_id" cannot be used within a formula for report calculated fields. This is limiting since it means we need to create a custom field to be based on these fields to use within the formulas. Consider...
Karla Johnson
about 4 years ago
in Integrations
0
Future consideration