ADD A NEW IDEA

All ideas

Showing 8997 of 8997

Slack Channels for Features

It would be very helpful to have Slack Channels per Feature. At this moment all changes in features comes to the same channel, mixing information from different features that affect different groups. Therefore, having the ability to create an inte...
Pablo Antolín almost 9 years ago in Slack 6 Likely to implement

Ability to add comments to the link records or the reason for dependency.

What is the challenge? Not able to comment to why a particular linked components are dependent of other one. What is the impact? For certain dependency to be created there are some additional comments required hence we are looking for a comment to...
Guest 6 months ago in Dependencies / Features 0 Future consideration

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 6 months ago in Reports 0 Future consideration

Consider inherited values when copying workspace settings for workspace templates

Who would benefit? Any users creating a workspace template from an existing workspace. What impact would it make? Today if a workspace template is created from an existing workspace, Aha! does not look at inherited settings. For example, at the wo...
Kristina Gass 12 months ago in Account settings 0 Future consideration

Create User story maps at a workspace line level

For large Teams that are organized with multiple scrum teams that all contribute to the same user story map, it would useful to be able to create a user story map at the workspace line level, and incorporate features from different underlying work...
Haga Rabekoto over 2 years ago in User story map 0 Future consideration

Displaying requirements within the Retrospective report

Who would benefit? Our dev management team What impact would it make? Would provide much better insights into why a release went off track. Currently the "Records Added" section lists Epics & Features added after dev started. In our case, it's...
Sam Banks almost 1 year ago in Releases 0 Future consideration

Capacity for teams: API support for team schedules

Ability to create and update schedules via the API. This would allow us to automate team availability (user's PTO or maternity/paternity) and easily update company holidays.
Nathaniel Collum over 4 years ago in Account settings / Capacity planning 0 Future consideration

Bulk edit "custom table relationship" custom fields

Bulk edit is not currently available for "Aha! record relationships" custom fields, nor "custom table relationship" custom fields. Adding the ability, at least for "custom table relationship" custom fields will go a long way to increasing usabili...
Guest almost 6 years ago in Account settings 0 Future consideration

Custom scorecard components/elements are available for reports but NOT for integrations.

We actually would like to display the individual pieces that comes our WSJF scorecard for our initiatives in Aha. Right now, I can pull the individual scores into an Aha report, but I'm not able to send the same data to JIRA. We use dashboards in ...
Wen-Wen Lin almost 5 years ago in Jira 3 Future consideration

Enable Admins To Publish Reports

Administrators often manage Product Portals (because only admins can create new ones), and therefore it is limiting for admins to have to request from each report owner to update Share Settings. Admins should have ability to change all data settin...
Guest over 1 year ago in Application / Ideas portal 0 Future consideration