It would be really beneficial to have an option to show Jira Status in any card view as to have more granular detail when you need to communicate with the devs, or to report status to other stakeholders.

I am creating a custom roadmap which lists all of our initiatives we plan to deliver in 2021. Some are being delivered in Q1, Q2, and Q4. Because there are no initiatives being delivered in Q3 - the column for Q3 doesn't appear. This causes confus...

When I enter the Overview in roadmaps-libary always the setting is set to "my reports". But I have to see all reports of my team. Sometimes I'm only looking for my reports, but I always want to see all the reports.

Each one of our features is linked to a designated release phase. We would like to be able to better view this on the features board by ranking features by the release phase. I have added the release phase to the custom cards for features-which is...

When SSO is used and a user attempts to access the company aha instance, they are presented with a list of the emails of the people who have billing permissions (not sure if only when the account does not have available seats). Either way, compani...

I like the opportunity canvas format. It stores a lot of detail and serves as a jumping off point to an epic and/ or feature. If they are linked, I can easily see everything I have related to the canvas and reference quickly when my team is review...

would be nice to create more custom fields for ideas to guide our contributors on how to ask for ideas.

Im trying out the new Slack to AHA integration - it works great but is it possible to limit the interactions a user can make with AHA? I want to limit my teams options to just being able to raise ideas through slack - and not iniatives/releases et...

Problem If a Version is exported from Aha to Jira using the integration, and a fix version with that same name already exists in Jira, Jira will response with HTTP status code 400, and a JSON payload: {"errorMessages":[],"errors":{"name":"A versio...

Ability to use the At Risk flag and comments for automation tasks eg when a feature field is updated. Or be able to use the At Risk flag and comments as fields in Integrations eg integrate the status or field from execution tools like Rally to fla...