Webhook data from Ideas is split in two messages and is missing Category and custom fields
When a new Idea is added in the Ideas Portal, we get 2 separate "added idea" HTTP requests. The first only contains the Description field. The second contains the Name field and a few other fields. This makes it very difficult to take an action in...
Guest
over 8 years ago
in Ideas portal
1
Unlikely to implement
Would like the ability to customize the AHA feature number to auto default to the integrating Jira ticket number? It is difficult to locate features in Aha while working with my developers, who work in Jira. Currently we are integrating one of our...
Christina C
about 4 years ago
in Features
1
Future consideration
In order for developers to be able develop exactly what is required, validation or acceptance tests must be added to user stories. Each User Story should be able to have numerous Acceptance/Validation tests. This will assist in assigning effort an...
Guest
over 8 years ago
in Features
0
Already exists
set a filter to only show dates that do not have any activity scheduled. It is helpful eg social media posts. I can see in which week I haven't planned any post yet and can strategically plan a additional activity.
Leonie Mandelkow
about 4 years ago
in Calendar
0
Future consideration
When comparing ideas, I'm interested in relative effort and the resulting quadrant classification. However, almost all of our ideas have effort in the range 5-40, and this puts all of them in the "Maybes" and "Easy Wins" quadrants.
I'd like to be...
Guest
over 8 years ago
in Ideas
0
Future consideration
I need to be able to attach a file, to a customer layout of a Change Request Epic (Master Feature) in order to ensure finance data is populated and held against the Change Request. This is a standard form and I would like ot be able to have that f...
Becca W
about 4 years ago
in Epic
0
Future consideration
Hi there, I have identified a problem that might be good to find a solution for. When using workflow view, default swimline setting is based on user picker. It would be a quick win to have a button that would automatically pick users that have ass...
Daniel Pokrývka
about 4 years ago
in Features
1
Future consideration
Sometimes our QA or Doc teams will reject a requirement because they have questions or additional clarification is needed. Once they are satisfied with the requirement they would like the ability to go back and approve it. This way we don't have t...
Sikia Soller
about 4 years ago
in Features
0
Unlikely to implement