As we continue to expand our use of Aha, one issue that has come up is that within a given product, there are different types of work/requirements that require different types of information. We're adding more and more custom fields, and it's star...
Zach Rose
about 8 years ago
in Features
8
Future consideration
Expand/Collapse Release View to include Requirements
It's critical for our teams to see Features AND Requirements on the Release (Overview/Details View). You should be able to continue expanding down the hierarchy from Epic > Release > Feature > Requirement all within the Gantt.
Guest
about 6 years ago
in Releases
7
Future consideration
Global feature to filter out internal votes displayed everywhere in Aha!, especially in the Ideas Portal
Our organization promises to review and take some action on any idea that receives over 25 votes. We don't count internal votes toward that total, but internal votes will push it over that threshold. The main problem is that the customers only see...
RICH O'FARRELL
over 1 year ago
in Voting
4
Future consideration
Synchronize Aha! organizations custom field with Jira Integration
What is the challenge? We heavily use the Organizations custom field in Aha to map customer engagement and roadmap transparency and need that info to sync to our Jira instance. What is the impact? Disconnected systems, duplicate data entry, poor u...
Not just the fields present in your epic/release/feature/idea template. I have flows for each of these record types that add new fields for input later on and would like to run automations on them, but can't unless I add them to the template used ...
Danielle A
about 3 years ago
in Workflow boards
1
Future consideration
Map github username with aha emails for github-aha integration assignees sync
What is the challenge? aha-github assignees integration do not work What is the impact? cannot make use of the assignees sync in the integration Describe your idea In the Aha! Github integration the assignees are not getting synced. In Github we h...
Ankit Bapat
8 months ago
in GitHub
0
Future consideration
Require completion of certain fields with promoted ideas
Epic, feature and initiative layouts allow you to require certain inputs when these records are created in the platform. But if they are promoted from an ideas, portal, individuals are able to bypass the completion of these 'required' fields.
Danielle A
about 3 years ago
in Ideas
4
Future consideration
What is the challenge? When moving from a ZenDesk knowledge base to an Aha! knowledge base, currently each document must be uploaded to Aha! individually. What is the impact? This would improve the speed for migrating tools. Describe your idea Add...