Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Features

Showing 1190

Only send Aha Feature Name to Jira Summary once - while not breaking Integration 2.0

My use case is the following: Product wants to shorten the Aha Feature Names so they look better in Aha's roadmap views. On the other hand, I don’t want Aha to overwrite my more descriptive Summary on my Jira tickets. How do I set up the integrati...
Guest about 6 years ago in Features 0 Future consideration

Automation Rules for Features or Epics

It would be awesome to be able to add automation rules for Features or Epics. For example, if a Feature state is set to At Risk, then the related Epic & Initiative can be set to At Risk. Or, when the first feature related to an Epic or Initiat...
Guest about 2 years ago in Features 0 Already exists

Don't allow duplicate "tags" with grammatical differences, caps/no caps, etc.

Tags – the Aha! system allows you to create the same tag multiple times with “caps” & no caps. Example: “National” and “national” – they are created as separate tags, even though it's the same thing, just grammatically different. The tag list ...
Guest over 8 years ago in Features 0 Will not implement

Allow Custom Descriptions (Tool Tips) for Default Fields in Layouts

Aha allows the user to create a description (tool tip) for custom fields within a layout, but you can't add descriptions to default/native fields, like the "Type" field at the Feature level. Given that the Feature "Type" field is completely editab...
Zach M about 2 years ago in Features 0 Future consideration

Link Program Epic field on Team Epics, to Program Epic field on parnet Features

I work at Nike and I know we use some slightly different names to describe things within Aha to fit our culture, so hopefully you can follow this: If a user has the Program Epic field set on the FEATURE and on the TEAM EPIC, the Aha system does no...
Guest about 4 years ago in Features 0 Future consideration

new feature creation (copy an existing), like for releases

I like the possibility to copy existing releases, when I create a new release for another product. I can imagine, that it would help many AHA users, including me.
Tobias Michels about 4 years ago in Features 2 Future consideration

Customize cards on the details view

Challenge: I love that you can customize the cards on the features board to align with how your team works. However, when I then view a details page, the card is not customized in the same way. Desired experience: I would love to be able to custom...
Julie Price about 4 years ago in Features 0 Future consideration

Ability for 'product owner' to adjust other users time logged if necessary

Hi Would be a great asset to us if the 'Product Owner' level of access or some kind of admin access had the ability to update/adjust time entered on other users behalf for various reasons such as: another user has logged time against a feature ...
Guest over 8 years ago in Features 1 Already exists

Allow feature to be associated with more than one master feature

Some of the features we're developing will support more than one master features. Currently there is a limitation that a feature can support one and only one master feature. This falls short for us and doesn't allow us to see where investment in o...
Perri-Anne Sims over 6 years ago in Features 0 Unlikely to implement

Copy a feature from Product to Product and get the Aha ID from the new product.

Can I copy a feature to a different product AND get an Aha indentifier that begins with the different product prefix? Right now if I move a feature from Promote to Store Fulfillment the copied feature gets a PROMO ID and not an SF ID. If I copy, c...
Tammy Connell over 6 years ago in Features 0 Unlikely to implement