In automation rules, evaluate the fields on the triggering object (feature, idea etc.) to set conditional actions
When creating automation rules, we need to know what field value is on the idea that is being created before doing an assign-to action. Right now I can only define an assignment to on ANY idea, which I can already do with default assignees. Give t...
Christopher L
over 4 years ago
in Account settings
0
Already exists
Add gmail Quick Actions so action can be taken quickly
This would reduce the number clicks a user would need to take to get to an Aha link embedded within an email (i.e. Comment Notification for an Idea or Feature card).
JIRA has a View Comment and Gmail has a RSVP quick actions that allows a user to ...
Allow to set the created_at time when creating internal comments via API
While setting the "created_at" attribute when creating public comments for ideas via the API works smoothly, the same doesn't work for internal comments. The endpoint used is https://quintly.aha.io/api/v1/ideas/<IDEA_ID>/comments as a POST r...
Frederik Born
almost 8 years ago
in Ideas
1
Unlikely to implement
There are times when a Master Feature gets released into multiple Releases. It would be nice to see the master feature and all the releases associated with it form the Gantt Chart.
Guest
over 4 years ago
in Epic
2
Unlikely to implement
Please allow to adjust the background Color, even a light gray works better. White background is hard on your eyes for any kind of longer session use. It limits how much work I can do at a given stretch. It also washes out the presentation slides.
Guest
over 4 years ago
in Account settings
1
Future consideration
Allow for strategy overview tab names to be configurable and allow for default components to be set at tab level
I am configuring Aha to use with internal IT applications and services. I'd like to be able to use the Strategy Overview to define and display product purpose and other attributes, but the terminology doesn't fit. I know I can completely customize...
Guest
almost 8 years ago
in Strategy
2
Unlikely to implement
Trigger Automation of requirement cards based on Feature status
As a developer, I need to ensure that I have a peer code review and test my code. I track that its complete and who did it by creating requirement card and assigning it to another developer. This allows the PMs to track that that was complete. I c...
Guest
over 4 years ago
in Features
1
Future consideration
Make fixed workflow transition enforcement optional for Jira integratations
Jira is our source of truth for synced items, so if Jira somehow allowed a status change to happen we don't want Aha! to [almost] silently ignore it.
With the current behavior, any discrepancy makes Jira and Aha! grow apart and we really need A...
Daniel Hirschberg
over 4 years ago
in Jira
0
Future consideration
fix intermittent bugs in how arrow keys work in epic description
When editing a capability description in Aha (such as https://niceactimize4.aha.io/epics/XPROG-E-503?active_tab=description&full_screen=7154518607894442779) (our capabilities might be your epics), using left and right arrow keys moves the curs...