ADD A NEW IDEA

Application

Showing 770

It should be possible to "block" release dates

Playing with gantt chart can cause a lot of problems, especially when moving releases/stages/features using mouse - it will be great to have a chance to block dates. In my opinion it should not be possible to change "scheduled" and "shipped" relea...
Guest over 8 years ago in Releases 1 Unlikely to implement

Feature Card Print

In general our portfolio workflow involves us managing our backlog in Aha, but then creating a physical board that has all the current and upcoming features on a standup board where all of our team members can gather and discuss. Working only onli...
Guest almost 8 years ago in Features 5 Unlikely to implement

Allow Idea Portal Users to Export Ideas

Add the ability for Portal Users to export the list of ideas they currently have displayed on the screen. This would allow ideas to be shared within an organization / client for users who do not have access to the Idea Portal or choose not to use ...
Guest over 7 years ago in Ideas portal 2 Unlikely to implement

Allow idea portal SSO to use the main account SSO for auth

I would like the option to reuse the SSO from the main Aha account SSO for any idea portal we create. So in the idea portal SSO tab, you could pick the Aha account SSO to use for auth on the portal. My struggle at the moment is to have our securit...
Brian Carr over 7 years ago in User management 3 Unlikely to implement

Configure so that master features and feature dates are following release dates

I would like to be able to configure so that the master features (MF) and features (F) follows the release date. This would be very helpful during sprint planning and replanning. The bulk editing is a work around, but still when you move around th...
Kristian Haglund almost 5 years ago in Epic 1 Unlikely to implement

Automatically create new copy features in other workspaces based on feature tags

Who would benefit? Any product owner that has multiple workspaces or multiple tiers of workspaces. What impact would it make? Reduce the amount of work by creating tickets once instead of copying and moving. Further, changes in the feature in one ...
Guest 7 months ago in Features 1 Unlikely to implement

Comment fields: Any one with contributor status should be able to update the comments field and should be ordered newest to oldest

The comments field is used by several people to comment on status, updates, questions etc. Contributors should be able to add update comments started by other people to keep the thought thread together. Also, they should have a sort order provided...
Guest almost 4 years ago in Comments / Notifications 0 Unlikely to implement

Make the JWT claims OIDC conformant

The first_name and last_name claims required by Aha! are not OIDC conformant, leading to duplicate information in previously conformant JWT tokens. This increases the size of tokens. This can also make it harder to use a common token for Aha! and ...
Guest almost 4 years ago in User management 2 Unlikely to implement

Granular Permissions for Components

It would be beneficial to Product Line Managers and Product Managers if individual custom components could be hidden from some individuals. This is useful when adding sensitive financial data or other secure information. If the Product is shared f...
Guest about 9 years ago in Product 7 Unlikely to implement

Ability to widen the column size on the Features Board

I have a lot of features in the parking lot, sometimes I have a lot of features in a release and want to see them all on the screen at once. If I could adjust the width of the columns and then have all of the features move and "tile" within the ad...
Guest almost 7 years ago in Features 3 Unlikely to implement