Skip to Main Content
ADD A NEW IDEA

All ideas

Showing 8958

Add workspace name as a field on records

What is the challenge? Aha! allows teams to build complex roadmaps with work from across a portfolio contributing to an overarching endeavour. When reporting on the work rolling up, it's necessary to see which workspace that work belongs to. Aha! ...
Steve Dagless 5 months ago in Reports 0 Future consideration

Have a report view be dynamic in notes/documents

When adding a report into a document/note via "aha view", the view of that report does not update after you edit the report. One of the great things about Aha is how data driven the tool is. Unfortunately the way views show reports in documents/no...
Matt Toburen over 1 year ago in Notes 0 Future consideration

Allow for mapping to-dos in Asana integration

In some cases, Asana sub-tasks are more closely related to Aha! to-dos than requirements. For example, a feature may have to-dos related to marketing tasks which need to sync with Asana. An option to map To-dos to Tasks or Subtask would provide a ...
Austin Merritt over 6 years ago in Asana / Integrations 4 Future consideration

Resend activity webhook events on errors

Currently, if an activity webhook event fails to be sent - we have no way of resending the event - regardless what error is sent. It would be ideal if: 1) There was an automatic resending of failed events after a period of time. 2) A way to manual...
Guest over 1 year ago in Integrations 0 Future consideration

Allow Default capacity Planning to be inherited from company

It would be great to set the option for capacity (time/point) and also if to capture at task or feature level, so when I add a new product it is already set. AS it stands, every new product I have to go in to config, turn it on, and switch from ti...
Jon Ellis over 6 years ago in Application 1 Future consideration

Allow sub-releases to have independent release dates from a Rollup Release date

We're operating in a CI/CD environment, and prefer to release "releases" (especially API's) as soon as they clear integration and performance testing. Forcing all of the sub-releases in a Master Release to inherit that release date is not meeting ...
Guest over 8 years ago in Releases 11 Unlikely to implement

Include link to relevant automation rule in record history

In the record history, include a link to the automation rule that triggered something to happen so that I can quickly figure out which automation rule caused the change to happen. Currently it can be hard to figure out why something happened when ...
Todd Meyer 5 months ago in Application 0 Future consideration

Can we have the progress set to 100% on release items when they are closed?

What is the challenge? Manually editing the % progress is a pain What is the impact? Loss of productivity Describe your idea Make it editable in the UI and workflow to auto set to 100% when the ticket is closed.
Guest 5 months ago in Features 0 Future consideration

Set recurring todos from automations

Who would benefit? When setting a todo using an automation, there is often the need for the todo to repeat over the life of the record. What impact would it make? Currently I would need to manually set a todo to recurring and cannot use an automat...
Max Robbins 10 months ago in To-dos 0 Future consideration

Dual Track Roadmaps

If your roadmap goes out further than a couple of months then those items further out are doing you a disservice. To anyone looking at that roadmap, they look like things that you are definitely going to do. Even worse is the fact that those item ...
Guest over 5 years ago in Roadmaps 0 Future consideration