Skip to Main Content
ADD A NEW IDEA

Application

Showing 7147 of 8637

Restrict Access at lower levels of product hierarchy

We need to be able to restrict access at lower levels of a product hierarchy. e.g. Reviewer at BU & Division, Product Owner for Product 1, None for Product 2. Our hierarchy is BU -> Division -> Product Line -> Product. We want everyo...
Wes Gillette over 7 years ago in Account settings 1 Unlikely to implement

Downstream configuration of terminology

I want to use one set of terminology at the Product Line level and another set within its Products. ie, Initiatives at the Product Line level and Epics at the Product level. Allow me to set the terminology for all products in a product line's co...
Max Cascone over 7 years ago in Releases 0 Future consideration

Update idea status to "will not implement" when related story will not be implemented

As a story evolves from an idea, it may be decided that the story is not worth implementing. Currently it doesn't seem that story status changing to "will not implement" will also update the related idea.
Guest over 7 years ago in Ideas 0 Unlikely to implement

Constrain Releases to Initiative dates when linked

When creating Releases and linking them to Initiatives, it is easy to forget the date ranges you set for the Initiatives. It would make sense for a Release's dates to be constrained to the Initiative's dates, or at least a warning that a release's...
Max Cascone over 7 years ago in Releases 0 Future consideration

Make it easier to add features to release phases.

Dragging and dropping is difficult and annoying. Is there a way we can have an "Add to phase" button like the one we see when adding an existing epic to the roadmap?
Jaclyn Fine over 7 years ago in Releases 3 Already exists

Allow number criteria when building a custom number field.

Make the field recognize numbers, but allow the customization of a number range. For example, 1-10. I tried to accomplish this with a predefined list, but it doesn't recognize the number as a value and therefor doesn't sort correctly.
Guest over 7 years ago in Features 0 Already exists

Make Requirements data available for hierarchy report.

The hierarchy report is very useful, however it could be improved by making requirements data available also.
Brian Stanley over 7 years ago in Reports 0 Future consideration

Allow to remove public comments from ideas via API

We are just about to start using Aha! and thus have imported comments from our existing system into Aha! ideas which went perfectly fine. Though now we realized it doesn't make sense to have these comments public, but instead create them as privat...
Frederik Born over 7 years ago in Ideas 1 Future consideration

Personas integration to Google forms

One of our ways to capture data about personas is to send questionnaire using Google form. It could be really amazing, if some of the fields in Google Forms will be integrated into Personas fields, it will save a lot of time and will robust the p...
Guest over 7 years ago in Strategy 0 Unlikely to implement

Provide Hierarchies and Dependencies for Features, Releases and Strategies

Just like Product Lines and Products, Features can have a hierarchy. Since Features have a Roadmap, they also have dependencies that should be allowed. BTW, this same logic would apply to Releases and Strategy since they have Roadmaps too.
Guest over 7 years ago in Application 0 Already exists