Features

When importing data to the Aha system, there are other id's that we use as keys such as Wave ID's etc. The goal is to be able to use other fields as ID keys so the system can identify the same key in the import data and update the system according...

When I'm looking at 1 or 2 releases, and 1 or 2 parking lots on the Features Board page - there's still a lot of white/unused space in the middle. At the same time, some of the feature names are wrapping, which means I can't see as many cards on t...

Right now adding features from the board view doesn't require going through a full form, bypassing mandatory fields such as effort estimation, epic etc. Please add the ability to open a popup when attempting to add a feature (with the text already...

It would be great to have the ability to print a card in a nicely formatted way. If there is a way to do this, I've not found it.

Hello! I've added some quality management fields to the bottom of our feature record since the admin section allows you to have fields at the top or bottom. However, it doesn't allow me to update the title and only calls the section " Custom Field...

I'd like to put milestone markers on the features board, so I can call out important, um, milestones, in the product's journey. It'd be great if they could be dynamically linked to the release milestones. Somewhat related to APP-I-794.

We use the roll-up initiative feature a lot at the line level and the initiatives at the product level. So all the features and master featured are linked to the initiatives but when we look at the roll-up initiatives, we are not able to see them ...

We want to automate the user provisioning and make sure we don’t provision users beyond the allocated count. Hence we want to leverage API to get the allocated user count .

It'd be really great to be able to see all outgoing emails that are sent along with a delivery/viewed status. This would allow us to better support our customers by seeing/ensuring they receive our notifications and in allowing us to audit exactl...

Since Bugs are not 'first class' entities in Aha and the suggested workaround is to map requirements with bugs in JIRA, we have done that and use a custom field of type in requirements which has the value of bug and story. However, when we open a ...