Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Aha! Roadmaps

Showing 5653

Support the ability to change a Jira project key

Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.
Wayland Fox almost 4 years ago in Jira 0 Future consideration

Add "is blank"/"is not blank" filter option for "record links" filter type

For most filter options in a report you can choose to filter by fields that are "blank" or "not blank". This is not the case for the "record links" filter. It would be great to be able to also filter record links using the "blank"/"is not blank" o...
Finn Meyer over 1 year ago in Reports 0 Future consideration

Map VSTS/TFS picklist custom fields to Aha! choice list fields

VSTS/TFS picklist custom fields are treated as strings and cannot support option mappings. Mapping a picklist field to an Aha! choice list field should provide the option to click Configure and map the choices.
Tessa Adair almost 6 years ago in Azure DevOps Services and Server 9 Future consideration

Create Custom Layouts for Custom Tables

What is the challenge? I can´t create custom layouts for custom tables What is the impact? I can´t group fields depending on the end user priorities, I can´t turn field to read-only if needed, I can´t edit relationship data with other records Desc...
Edgar Holguin 8 months ago in Account settings 0 Future consideration

Support changing embedded report type

What is the challenge? If you create a custom report and add it as an Aha! view to a note, if you untick 'Create a copy', and then change the report to a different type (such as changing from pivot to list) it stops displaying properly in the note...
Daniel Campbell 8 months ago in Reports 0 Future consideration

Remove releases from features roadmap if all features/epics have been filtered out

Who would benefit? Product managers & their shared webpages What impact would it make? Allow us to not have to manually adjust releases based on goals/initiatives or other information that's not represented in that release How should it work? ...
Steven Schafer 10 months ago in Roadmaps 0 Future consideration

Add support to map Azure Boolean Fields to Aha

This request is to support the mapping of ADO boolean fields to Aha predefined droplist and tag fields. Currently, Azure DevOps Boolean fields (true/false) cannot be mapped to Aha fields. Rather, in ADO, you need to create a field as a picklist in...
Jerrold Emery almost 3 years ago in Azure DevOps Services and Server 0 Future consideration

add filter for to-do section on releases

What is the challenge? running a GTM i need to be able to remove completed actions; or sort by the date due or owner. What is the impact? at the moment i have to run a seperate report to achieve this flexibility; however, when using the report, i ...
Andrew Pearson 3 months ago in Releases 0 Future consideration

Custom field tied to a custom table should show all columns (or selected columns) from the table

We have a custom table with 4 different columns and a custom field (feature level) tied to this custom table to select a value. When I access custom field for selection, it only shows the first column in the table. However, I need to see all colum...
Ram Dhurjati about 3 years ago in Account settings 0 Future consideration

Automation to set a default estimate for all features created

I'd like the ability to set a default estimate for all features created. I checked the automation rules and the estimate field is not an option to update via automation rules. Some of our teams are doing a no estimates style of capacity planning w...
Guest about 4 years ago in Features 2 Future consideration