PINNED
Chrome extension to capture feedback from anywhere
What is the challenge? We work in many applications and Aha! can not build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? This res...
What is the challenge?
When assigning features in Aha that are then sync'd to Jira - the assignee field cannot be set
What is the impact?
When development teams use Jira and Product teams use Aha, the feature becomes the common currency. T...
Manesh Patel
6 months ago
in Jira
0
Already exists
In Roadmaps Overview "Folders" left navigation area is missing Folder Tree capability
The sub folder created in a folder in Roadmaps is not possible to see in the left navigation area. No expand functionality is available to expand the folder structure. Current behaviour: Just when selecting the folder the user can see in the canva...
Norbert Kociok
over 2 years ago
in Roadmaps
0
Future consideration
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 ...
Guest
about 7 years ago
in Jira
2
Future consideration
Release templates - ability to set default at parent line that is also then the default for all sub-products
The recent release template features have been great but as I have many sub-products within a parent-line, I have to go into each one to set the default release template. Please consider implementing a feature that allows you to force set the defa...
Dave Tucker
over 5 years ago
in Releases
0
Future consideration
Allow templates to be applied to records after they're created
When records i.e. epics or features are created in the user story map or starter roadmap view, they do not have their record templates applied. This is because you cannot select the feature type within that view upon creating the record. In cases ...
Allow Aha! user name to populate DevOps board user
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...
When using filters in Features, Releases, or Roadmaps, dynamically show options that are relevant to what has been filtered. This is already implemented when using a workspaces filter and a specific workspace or group of workspaces is selected. Th...
Jeffrey Ma
about 5 years ago
in Roadmaps
0
Future consideration
What is the challenge? To efficiently manage and present data within table cells. We often need to adjust cell sizes and alignments manually, which can be time-consuming and prone to inconsistencies. Ensuring that the auto-layout feature works wit...
Noel Scerri
about 1 year ago
in Whiteboards
0
Future consideration
We use Aha! Scores heavily on our features, and while Reviewers can see the aggregate score, they cannot view the values for individual metrics (Sales increase, Retention of customers, etc.). Many of our reviewers are members of our engineering te...
Guest
over 11 years ago
in Features
1
Already exists
What is the challenge?
integrations with jira accepted in a specific workspace, create those items in that workspace rather than the workspace they are supposed to go to
What is the impact?
A TOTAL MESS
Describe your idea
Define work...
Guest
6 months ago
in Application
1
Unlikely to implement