All ideas

Capacity for teams is currently available to set up at a daily, weekly, monthly and quarterly. It would be helpful for teams that are planning sprints, to be able to set a capacity for each item (Theme/epic/feature) per sprint. Once this is done, ...

The idea here is to be able to react directly to a comment, thus creating some kind of thread. The goal is to provide better insight on a context explained by a portal user, react to an answer, like/vote for a comment especially relevant, etc.

Presently, you can map types for items at the Feature level and this syncs between Jira and Aha! without issue if the item type changes in Jira; However, the issue that we are facing is that because there's no mapping between Jira and Aha! for req...

What is the challenge? When I create records from the + button, often I need to get back to them soonish after creating them (but not always right away) What is the impact? It's more work than it should be to get back to the record I created Descr...

What is the challenge? When running standup (or in other team ceremonies), we often call out a card by its number (CORE-XXX) instead of its name. What is the impact? We scan the current board while looking for the card in question. This is a daily...

Currently when creating a feature, I have to create the feature and then manually send the integration to ADO. I want to have a variable on the Create Record Layout screen to be able to choose this option when creating the feature. This way I can ...

We use Benefit Maps to help plan out work and recieve Business approval. The content of the map is all on Aha such as Company goals, initiatives, and often features. The latter two typically come through the our Ideas portal. It would be beneficia...

I would like to be able to set a filter in my Integration for which Jira Issues to sync up. An example would be to not push stories into Aha until there is a point value or time estimate entered in Jira. Another would be to only push to Jira if it...

Most users spend their time in features boards and therefore are unlikely to see broadcast messages which limits their usefulness. We recently had to notify users of a change and had to send an email to ensure they were aware of what was changing

I am managing a few master releases right now with dates that are moving around, and it is currently time-consuming to send updated release dates of all sub-releases to Jira (and easy to miss one!). I’d also like the ability to reshape features, e...