Automation rules today require a great deal of repetitive configuration as they currently lack the ability to query for a set of data and then use this later in the workflow. For example when updating a Feature that references a custom table I'd l...
Michael Bruner
over 2 years ago
in Features
0
Future consideration
Allow me to self-subscribe to a report with an Aha! link
You recently introduced the ability to schedule delivery of reports. However, let's say my team member creates an interesting report, and I'd like it delivered weekly. I must first make a copy of that report in order to schedule it. But there's a ...
Nathaniel Collum
over 2 years ago
in
0
Future consideration
While trying to import records from Jira into a workspace, received the following error: * 10 Requirements - Import error: Please contact support@aha.io for help. It was not clear to me that the errors could be found in the Log messages and only d...
David O'Hare
over 4 years ago
in
0
Future consideration
Adding avatar icon/pic on each ToDo, Requirement/Feature list in order to easily identify if it is assigned and to whom
A Feature has been created with a number of Requirements and each of the requirements have a number of ToDos which need to be done - in many cases by different people. We are a having a self organizing team - I create the feature and inform the te...
Guest
over 6 years ago
in To-dos
0
Future consideration
Who would benefit? Anyone that promotes ideas to other records and uses the feature/epic (other boards) to view record cards What impact would it make? without clicking into a record, I would be able to quickly reference if an idea was the origin ...
Michael F
11 months ago
in Account settings
0
Future consideration
Who would benefit? Users checking the history, who will be able to reduce the noise What impact would it make? It could be possible to reduce some "spam" in history to make it easier to focus on the information which is required How should it work...
Nicola Rolando
11 months ago
in Application
0
Future consideration
We need a burndown at the master release level. We have multiple product groups working together and we need to see a burndown for all of the work combined.
Ashley Powell
over 4 years ago
in Releases
1
Future consideration
As an Aha user, when I create a Requirement with a Comment which is mapped to Azure DevOps I need the initial Comment to synch to Azure and not just subsequent Comments Working with offshore teams, and not able to speak to them during off hours, w...