PINNED
Chrome extension to capture feedback from anywhere
What is the challenge? We work in many applications and Aha! can not build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? This res...
What is the challenge? Unable to change the font type of text on a whiteboard What is the impact? Exported whiteboard images or web page views do not align with our company styling and are not suitable to be embedded into other documents due to th...
Alex Probyn
over 1 year ago
in Whiteboards
3
Future consideration
Make "release quarter" field filterable in reports
We create pivot reports to show our quarterly roadmap of features. Each row is an initiative. Each column is the "release quarter" field. Features are listed in the cells. This works great.
Now, imagine there are 4 quarters in the past, but you on...
Guest
about 8 years ago
in Reports
6
Future consideration
We would like to be able to map a JIRA fix version (and its dates) to an Aha Release phase
Why? We like to plan in Aha using a monthly program increment primarily with features, similar to SAFe. But as a continuous delivery shop using Kanban key t...
David Vins
over 7 years ago
in Jira
9
Future consideration
Include linked record/relationship field as an option for automated scorecard metrics
It would be valuable to be able to include standard fields that are derived from linked records in automated scorecard metrics. For example, I may want to create a metric that assigns a score based on the name of the goal(s) that a feature is asso...
Brittany Rhoney
over 2 years ago
in Features
2
Future consideration
Allow setting approvals to "any" or "all" when configuring automation rules to trigger approvals
Who would benefit? Users who require all members of an approval group to grant an approval What impact would it make? Right now it only allows "any" member which allows approvals in this scenario to proceed prematurely How should it work? Much lik...
Stephanie Lechner
about 2 years ago
in Automations
1
Future consideration
Jira Portfolio adds the Team custom field to JIRA. This team is used in Portfolio for planning. Aha! should support mapping this custom field so that the assignment of work and resource planning can be synchronized between Jira and Aha!
Scott McLean
over 5 years ago
in Jira
1
Future consideration
Add the ability to color code Epics in the User Stories/Features Board
When viewing the User Story/Feature board, it would be great to be able to color code the Epic nested above the User Story. This would help to be able to visually differentiate all User Stories that are associated an Epic. The user should be able ...
Mikala T
over 5 years ago
in Features
0
Future consideration
We would like to be able to make better use of Aha To-Do's so that they carry over to our JIRA Agile installation. Currently we have Initiatives mapped to Epics, Features Mapped to Stories and Requirements Mapped to a custom JIRA type of Requireme...
Guest
over 10 years ago
in Jira
5
Unlikely to implement
Teams can inherit delivery risk settings from the team line.
One can set delivery risk settings on the team line but these appear to have no effect. It would be nice to have teams be able to set their delivery risk settings to inherit from their team line, similar to how card customizations are intended to ...
Paul C
almost 3 years ago
in Features
0
Future consideration
Our company would like to implement a standardized theme for the presentations, but we need Source Sans Pro and Source Sans Pro Semibold to align with our PowerPoint templates outside of Aha!
Guest
over 5 years ago
in Presentations
2
Future consideration