Create a read-only custom field in Aha which is only populated and subsequently amended by an integration mapping
Map a custom field (on any layout) to an issue field in Jira (for our purposes, other institutions will have different integrations) where the population of that field occurs in a single direction (Jira to Aha!). Once populated in Aha!, only the i...
The recent update of the scorecards (which I generally like) comes with waaay too short labels. Generally I don't see a reason for the cards being so tiny and labels being truncated. Bigger cards, allowing for more (meaningful) content, would be v...
Improve usability of DevOps iteration field mappings as it relates to import
Azure DevOps does not support webhooks on iterations which means that updates to fields on linked Iterations will not flow from DevOps to Aha! However when specifying the Iteration field mappings in the DevOps integration in Aha!, it is possible t...
As an account administrator, I would like the ability to export a list of all my users to a .csv file and include information on their last login as well as their user role access to the various product/product lines in my account.
Name
E...
Home page: Allow tables, lists, charts or roadmaps to be set as the default view
As a product manager I use the board view all the time. However, when sharing with wider teams within the business, engineers particularly prefer a table view of features/requirements for a release. In the two organisations where I have used Aha!,...
Kevin McIntyre
over 1 year ago
in Application
1
Shipped
When Aha! users submit ideas via the public portal, make those ideas visible to everyone
Every time someone from out team (with account on Aha and logged in) submits a new idea on our portal (e.g. http://syncano-solutions.ideas.aha.io) the idea becomes private and then we have to manually change it to public. Could it be possible to h...
When copying a feature, copy the todos in it as well
Currently when copying a feature, the requirements within it are copied but any existing todos are not copied across. Todos are great for capturing the meta-work associated with a feature and the various tasks different teams need to perform to co...
Justin Woods
about 8 years ago
in Features
2
Shipped
JTBD: Link relevant external (outside of Aha!) documents to a record in Aha! so that I can keep information organised in one place. Problem: I have many external (outside of Aha!) documents that are used throughout the discovery, design, and imple...
Notify the appropriate users when they need to evaluate a work request
Work requests are a great new feature, and it's great that they can be assigned to workspaces. However, there needs to be a way for the appropriate users to be notified that there is a new workspace that needs their attention.
Mark Eaves
over 3 years ago
in Application
0
Shipped