Whiteboard templates to separate multiple iterations with stickies to relate to features. Stickies all began within the right columns (underneath the blue stickies). Blue stickies were the SAFe epics (Aha! initiatives), green and orange stickies a...
Laurel McHugh
over 1 year ago
in Whiteboards
0
Future consideration
Similarly to how custom fields can have optional descriptions. The same would be good for tags, so that additional information (essentially explaining the tag in more detail) can be conveyed to other users. This would reduce the need to either cre...
Sam Banks
over 4 years ago
in Features
1
Future consideration
Hi,
It's been requested from our own portal users that they have the ability to navigate between ideas in the portal based upon a previous idea and next idea links. Ideally this would navigate them through the current filtered list:
e.g.
My ...
Mark Evans
about 6 years ago
in Ideas
0
Future consideration
Show Initiatives Roadmap in the style of the Features roadmap
The pretty format of the Features roadmap, with the releases pinned as a circle on the timeline, looks great and really has an impact to show the future of a team/project.
I would love to show the Initiatives in the same format, to increase the i...
Max Cascone
almost 8 years ago
in Roadmaps
1
Unlikely to implement
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