What is the challenge? Currently in an ideas portal layout, the idea name must be present on the first "step" of a dynamic form. It can be helpful for a user to go through other questions first before entering their idea name. What is the impact? ...

For an app I was thinking of a desktop application, similar to the Notion app. I love browser things, but having a desktop app helps with multiple desktops and application switching. For mobile I could see a viewer for whiteboards being useful and...

Services published to our users typically all have a banner stating that they are accessing corporate resources along with some verbiage about their responsibility for securely handling corporate IP. This is an enhancement request to add such a fe...

Who would benefit? Customers using the Asset object through Jira Service Management. What impact would it make? When these Asset fields are added to Jira issue screens, this would allow users to map these fields to Aha! fields through the Jira int...

Our data model is such that every workspace in Aha! maps to a platform and we use a custom table to define the mapping. Since the field is mandatory for all objects in said workspace, we make the field mandatory when creating new features. We can'...

When working with multiple users, we need to be able who created what, commented on or changed something. As of right now, the user name (Admin) of who configured the Integration (Azure DevOps Services) is the one that appears on every item in Dev...

Right now, even after we manually click "Send to JIRA" for the first time for a release, subsequent changes to that release ( for eg. Addition of a feature under that release) do not automatically go through to JIRA. We'd want to have all changes ...

Currently there's a create a related Idea in the action menu for a feature. I would love to have Create a Related Feature option so that when the feature is created, there's a relationship immediately established.

When a feature is sent to Rally, also create predecessor and successor links according to feature links which exist in Aha! Changes to predecessor and successor links in Rally should create or delete feature links in Aha!

We have teams with several projects and creating it through templates is not practically scalable, hence require an API to create JIRA integration manually