Skip to Main Content
ADD A NEW IDEA

All ideas

Showing 8967

Change text color for Tags

What is the challenge? Using a light color tag makes the white text illegible. What is the impact? One can only assign dark colors to tags. E.g., one cannot create a white tag, a yellow tag, or a very light pastel tag. Describe your idea Allow the...
John Curtis 5 months ago in Account settings 1 Future consideration

Nested To-do's

What is the challenge? Currently to-do's are finite meaning we need to raise a pile of them and they do not show dependencies What is the impact? Long dislocated to-do list Describe your idea Allow for to-do nesting and dependencies
Guest 5 months ago in Notes 0 Future consideration

The Popups are annyoing

What is the challenge? How to turn off the popups? What is the impact? The popups are annoying. Describe your idea Your licensing model is, let me call it confidentially priced. Therefore, please provide an option in Aha to turn off the popups!
Guest 5 months ago in Account settings 1 Already exists

Customize "Vote" options to custom picklist or the basic facebook 'like' emotions

Voting on an idea is of little value in determining how your users will receive, or want to work with you, on an idea. Some users may vote for anything thats of any value, others may only vote for those ideas they really need. Its an ok data point...
Guest over 8 years ago in Voting 0 Already exists

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

Allow for custom layout templates to be built on other custom layouts

In our environment, we have created base custom layouts that all our teams need to use to apply standard fields common to the organization as a whole. However, most teams have a couple of additional custom fields they like to add to their workspac...
Karla Johnson over 3 years ago in Application 0 Future consideration

New features created via an ADO integration are assigned to the parent epic release by default

Key problem: the "Parent" field in ADO can contain only one value. In ADO, a feature is automatically associated to the same theme as its' parent epic, but in Aha! this is not the case. So when features import, we associate them with the correct p...
Bryan McElhinney about 2 years ago in Azure DevOps Services and Server 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

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