Skip to Main Content

Share your product feedback

ADD A NEW IDEA

All ideas

Showing 9041

Support mapping Asset object fields through Jira integration

Who would benefit? Customers using the Asset object through Jira Service Management. What impact would it make? When these Asset fields are added to Jira issue screens, this would allow users to map these fields to Aha! fields through the Jira int...
Stephanie Lechner 10 months ago in Jira 0 Future consideration

Allow multiple workflows in a product

Within a given product there can be different types of initiatives and features. Aha! supports the concept of feature types and allows templating of the description field by type. Would like to see an expansion of this concept to support configura...
Bonnie Trei about 5 years ago in Features 4 Future consideration

Link a Feature to multiple products

We regularly release features across Desktop, Web and Mobile which we have as separate products in aha. We would prefer to be able to have a feature which is linked across all products, as all are updated at the same time. We currently add feature...
John Hopkin about 9 years ago in Features 11 Unlikely to implement

Have the option to enable color-blind friendly mode where ever color is used (e.g roadmaps)

We have the option edit the colors for statuses via the Settings ⚙️ → Account → Statuses and workflows page; however, for users who have color blindness, changing the hue doesn't help much. We're looking to have the option for a texture or pattern...
aimee vitaglian over 3 years ago in Roadmaps 4 Future consideration

Support parent-child moving across workspaces and Jira projects

In the Aha! we have Features that reference a parent Epic in another workspace. In Jira we have issues that are children of an Epic in another project. This cross workspace/project relationship is supported in Aha! and Jira, but the integration do...
Michael Bruner about 3 years ago in Integrations 4 Likely to implement

Return unique values against linked epics/features

Using the worksheet at the release level; is it possible to return only "unique" values back against the "linked" epics/features? Example:Release - (linked to Epic 1, 2, 3)Custom Worksheet - Epic Vehicle Brands - Jeep, Dodge Epic 1 -Epic Vehicle B...
Guest over 3 years ago in Releases 0 Future consideration

Show custom field names on integration errors

When there's an integration sync error with Jira on a custom field, Aha shows something like this: 'customfield_19011': Please fill out required fields The identifier 19011 has no meaning to us, as Aha doesn't expose a mapping of our custom field ...
Brian Trombley over 3 years ago in Jira 1 Future consideration

Ability to copy or duplicate release phase

It would be beneficial and huge time saver to provide users with the ability to duplicate an entire release phase instead of duplicating features that belong to them for products that follow the same GTM process.
Sylwia Zalinska about 2 years ago in Releases 2 Future consideration

Reduce real estate consumption in the header section

Who would benefit? All users of Aha What impact would it make? It would show more of what matters on the screen, increasing legibility and user productivity. It would also bring the relevant content higher up on the screen. How should it work? The...
Craig B 11 months ago in Roadmaps 0 Future consideration

Add "Prioritization" to Releases

What is the challenge? I was actually trying to figure out a way to do this with a custom setup and noticed the prioritization screens for Features and Ideas. We need it for releases! What is the impact? Other than the order of the gantt chart and...
Bob W 7 months ago in Releases 0 Future consideration