ADD A NEW IDEA

All ideas

Showing 6289

Allow detailed estimates to affect capacity plans without needing to assign a team member to the Aha record

We do all of our assigning in Jira, and in fact only sync epics between Aha and Jira, so adding an assignee in Aha doesn't make sense for us as you don't assign a dev to an epic, even in Jira. We assign to the task/sub-task. Having to add an assig...
Jason Hollis about 1 year ago in Capacity planning 0 Future consideration

Email alerts (notifications) for Feature Due Dates

In Aha! - users only receive emails as a watcher, commenter, or via a To Do. Feature Due Dates are an important part of a created feature, and users should be receiving emails (similar to To Dos) when Feature Due Dates are upcoming, present, or ov...
Max Chanoch over 9 years ago in Features 0 Future consideration

Multiple Feature Boards

Allow to create multiple feature boards where columns can be defined by a different set of criteria. For example, I want to have one in a Kan-Ban style (with swimlanes https://big.ideas.aha.io/ideas/APP-I-4228 by a release) , another one with a co...
Anton Mamichev over 7 years ago in Features 1 Future consideration

Populate Jira Components via Integration

Currently, as far as I am aware, the only way to use Components from Jira is to add a custom field in Aha! and map them. This works OK, however if a new component is added in Jira you have to manually add it to Aha! as an option to select. Please ...
Guest about 1 year ago in Jira 0 Future consideration

Workspace - user search funcion

When a user has the custom role of owner and is a work request designee, it is not displayed on the Workspace > Users page as text. This doesn't give an accurate picture of user roles when searching nor does it tell you who the work request wil...
Melody Gibson about 1 year ago in To-dos 0 Future consideration

Restrict workspace type for new workspace set up

We have come across the issue of team members setting up different workspace types in our Business Line. This makes reporting complicated as the status do not line up. There should be a way to restrict workspace types for new workspaces with admin...
Guest over 2 years ago in Account settings 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 about 6 years ago in Application 1 Future consideration

Add ability to map record links for Aha! requirements with Jira records

Record links can currently be mapped between Aha! feature records and Jira records as covered here in this article. It would be helpful to have this same functionality to map record links between Aha! requirements and Jira records as well.
Jennifer Hill almost 3 years ago in  0 Future consideration

Tab ordering when adding a requirement makes it difficult to return to the title

Who would benefit? Keyboard users What impact would it make? Improve requirement adding experience. How should it work? When adding a new requirements, when you press shift + tab from the description field, it should go to the title and not the pr...
Will Lawrence 5 months ago in Features 0 Future consideration

Allow selection of which dashboard filters to use, instead of just on/off "use dashboard filters"

Who would benefit? Anyone merging information from different workspaces, timeframes, or other categories of data. What impact would it make? Allows one dashboard to be more flexible for multiple use cases. How should it work? Instead of a single c...
Kim Bremer 5 months ago in Roadmaps 2 Future consideration