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...
Have a Release Workflow Custom Status trigger the Send to JIRA action
In the end I just want to be able to manage the Send to JIRA trigger action via either my Features Workflow or my Releases Workflow. Send to Dev to me equates to send to JIRA. I will want to make sure my status is updated throughout, so I will alw...
Guest
over 10 years ago
in Releases
2
Unlikely to implement
What is the challenge? Although colors have been defined for a status, the color changes and shows as lighter when in views where the element appears as a pill. What is the impact? Only a cosmetic impact, and doesn't affect other use of Aha! Impac...
Becca Bommarito
over 1 year ago
in Roadmaps
2
Future consideration
Pie charts currently hide smaller data values after a certain threshold when data counts are turned on. This creates an incomplete user experience especially when the report is included in a presentation requiring workarounds such as attaching add...
Ashwina Blum
about 3 years ago
in Reports
1
Future consideration
Terminology customizations should persist throughout all screens when cascaded from Account level
We have updated some terminology for all of our products to use “Feature” (instead of default Master Feature), “Epic” (instead of default Feature) and “Story” (instead of default Requirement).
Unfortunately, this update in terminology isn’t consis...
Kirstin Maurer
over 7 years ago
in Account settings
0
Already exists
Release Phase Dates Determined by all related records
My last idea around being able to adjust Release Phase dates was rejected but our release phases are static (Closed Beta, Open Beta, GA) so simply adding another random phase isn't an option. This level of standardization is needed as we have very...
Guest
over 7 years ago
in Releases
1
Future consideration
When converting a requirement to a feature, if the original feature is in a shipped release, place the converted requirement in an unshipped release.
What is the challenge? I needed to break out a requirement in a feature that was already shipped (as was its release). However, when I converted the feature, it placed it in the shipped release. What is the impact? This new feature could have been...
Nathaniel Collum
10 months ago
in Features
0
Future consideration
Why were common editor buttons hidden under drop-downs ??? This is an unnecessary change and it's very inconvenient when working on features and requirements.
Guest
over 2 years ago
in Features / Notes
1
Future consideration
Our companies uses a few custom fields as part of our features. All of the custom fields that we use are notes. Enabling note-type custom fields to be bulk edited would be extremely useful.
Guest
over 6 years ago
in Features
1
Future consideration
We have adopted a SAFe framework where features are planned quarterly. As a result we are creating 'Releases' in Aha that are materializing these quarters. Within a quarter we may deploy the software multiple times and we are using release phases ...
What is the challenge? I work in a G suite company where all my work funnels those tools. What is the impact? I do not check or follow-up on Aha! to-dos because I don't have regular visibility. Describe your idea Allow a two-way integration betwee...
Guest
10 months ago
in Wanted
0
Future consideration