What is the challenge? Currently, scripted fields generated in Jira, even if they are Number fields, can only be imported as Text custom fields in Aha. This means their numerical values cannot be treated as numbers, only as text. What is the...

What is the challenge? Currently, there is no straightforward way to view or access Aha list reports directly within specific record types. Users must navigate to separately to access list reports, which disrupts workflow and makes it harder to ...

What is the challenge? Remembering to link the initiative to the idea after both have been created and having to click the Related link to view the initiative What is the impact? Adding steps in the idea creation process Describe your ...

What is the challenge? I am trying to find report of mine that I haven't used in a while to delete them. But I don't want to delete any have been shared in the event the user is actually using it, and I don't want to delete any that are being us...

What is the challenge? Want to use whiteboards for PI planning. Don't want User Stories as requirements in Aha. Have 100's of User Stories and Product Defects which we want to import. What is the impact? Allow team to use whiteboards for P...

My company has been migrating from GHE to GitHub.com, and the default repo permission is set to "internal". This is causing individual users to have access to over 15k repos. In Aha, this large number of repos is preventing users from being able t...

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

The whiteboard templates provided by Aha! have "Best Practices" defined in a side panel so that they content is not disrupted by the instructions for the template. It would be very handy to be able to add "Best Practices" to custom created whitebo...

It would save time instead of having to click 15-20 items in a list. If I could use 'select all' and then just de-select the one or two I don't want, this would be much more effiecient. Otherwise I'm manually clicking 15-20 checkboxes.

We would like to remove "requirement" from our custom feature layout as this adds "too many layers" to the work. We want to utilize "to do" only within our workspace.