We have over 250+ custom fields being utilized by various workspaces. Because we cannot assign a custom field to a particular workspace all 250+ fields are visible in every filter in every workspace. If we could have the ability to define which wo...

If the old mockup function is getting deprecated, it really would be nice if whiteboards were embedded into descriptions so that we can quickly create what we need to and have it as part of the attachments that flow into our dev systems.

Hi, I had a human-error issue where I had two users in my user list that I couldn't figure out how to give them view access. I clicked the viewer access button, but nothing would happen. It turns out it was because I wasn't clicking "allocate seat...

Sometimes people click when they didn't quite mean to or maybe change their opinion. Perhaps persuasive comments in the thread or other factors means they change their mind. However, seems there's no way for a user to undo or 'unvote' for an idea ...

There is currently an idea to include "Workspace" in the card layout. I would also like to be able to customize the card color by workspace (and probably other options as well).

When we change a domain, it would be good to autoforward from the old domain to the new domain, at least for a short period of time, to allow time for users to update bookmarks and links

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 using CSV import to integrate my Customer Support system (FreshDesk) with Aha!. The idea is that CS is our public interface and will receive and triage tickets (questions, defects, product enhancements, and incidents). Any valid defects/produ...

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...

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...