Skip to Main Content

Share your product feedback

ADD A NEW IDEA

All ideas

Showing 9120

Many-to-one custom fields should be clickable (like many-to-many custom fields are

What is the challenge? When accessing records in a custom table, if many-to-many custom fields are used, you can single-click the field on a record or in a report to open the context card. This does not work for many-to-one custom fields. What is ...
Perry Hurtt 7 months ago in Reports 0 Future consideration

Access your custom layouts to configure the Related tab for a record - be able to do this for linked records

Who would benefit? Product Owners/Managers What impact would it make? Easily be able to access linked record information from within the parent record such as engineering phase and engineering target date (custom fields.) How should it work? Enabl...
Guest 11 months ago in Account settings 0 Future consideration

Add Comment to Bulk Edit

It would be helpful to be able to add the same comment to multiple ideas at once. I use this to record when I have sent a group of ideas to a group or have done the same update to multiple ideas.
Guest about 7 years ago in Ideas 9 Already exists

DevOps Integration: Sync "Task" Workitems with Aha's "To-Dos"

Currently, our main work in DevOps gets done within Task items which also have effort spent inside. These however are not a sync-option within the "To-Do" level of Aha!. The fields "Name, Description, Assigned to, Due Date (and maybe effort or oth...
Michael Scholze about 4 years ago in Azure DevOps Services and Server 1 Future consideration

Customizability of workspace homepage

Who would benefit? All users What impact would it make? owner can customize the homepage they would like to highlight for team members. (for example: quick start guide note) How should it work? Owner can set default homepage for each workspace.
Ashton Tsou 11 months ago in Account settings 1 Future consideration

Aha! Develop - Reopen a completed sprint

It is possible to re-open a shipped release to make changes that should have been included. The same logic should apply to sprints as there are various reasons I may need to make changes.
Dale Potter over 2 years ago in Sprints 2 Future consideration

Roadmaps Improved Save Feature

Currently when we have multiple people updating the "Starter Roadmap" we find saving will overwrite previous changes if the previous save has not been explicitly loaded first. It would be nice to support "concurrent" editing and not losing changes...
Andrew P over 1 year ago in Roadmaps 0 Future consideration

Link Records: Ability to link presentations to features, epics, notes

We are using the notes functions for team meetings and agendas it would be amazing in the related section to link to specific presentations or reports. Similarly, we often create presentations that are specific for bigger epics to explain the func...
Nicole Hardin over 2 years ago in Presentations 0 Future consideration

Update the Release associated with an Epic or Feature using Automation

We've integrated Aha! Roadmaps and Jira but the release information is not being synced. We can use automation to copy the Epic/Feature Release name to a custom PI field and use the integration to sync the custom PI field with Jira. But when the P...
Sandy Kobayashi over 1 year ago in Roadmaps 0 Future consideration

Allow automation emails to be sent to non-user addresses

What is the challenge? We have centralized Product teams who prefer to monitor a shared inbox for idea submissions rather than their personal emails. What is the impact? Slower reaction to idea submission, confusion as to who has seen the submissi...
Guest 4 months ago in Application 0 Unlikely to implement