Who would benefit? Users of the portal What impact would it make? Allow more visibility to more items for those with larger screens. How should it work? Allow the frame that holds the roadmap to grow larger than it's current width. There is no rea...
Michelle Kish
about 1 year ago
in Ideas portal / Roadmaps
0
Future consideration
Ability to edit default terminology in report column headers
The default terminology of column headers of reports is not always explicitly clear on what it represents, which leads to confusion both internally and with customers when these report are shared out. As an example, clicking on an Organization pro...
Jeff Shaffer
over 1 year ago
in Ideas
4
Future consideration
Visualize when 2 or more features next to each other belong to the same epic
When ordering/prioritizing features in the features board sometimes there are features from the same epic with similar priority. If two or more features from the same epic are above each other, it would be helpful to visualize that they belong to ...
Niklas Gromann
about 2 years ago
in Features
0
Future consideration
Assign portal users to an organisation and limit votes to the organisation instead of user
We currently allow multiple users to join our ideas portal from the same organisation, this is due to different members of that organisation specialising in different fields and thus having different ideas based on their profession and different t...
Guest
over 1 year ago
in User management
0
Future consideration
We use master releases in Aha! since all products are shipped in one package. I set up a master release called template but I can't copy from it because you can only copy a release (not a master release).
Guest
almost 8 years ago
in Releases
1
Already exists
Who would benefit? When setting a todo using an automation, there is often the need for the todo to repeat over the life of the record. What impact would it make? Currently I would need to manually set a todo to recurring and cannot use an automat...
Max Robbins
about 1 year ago
in To-dos
0
Future consideration
Sometimes it is difficult to keep Jira and Aha Requirements up to date when/if a requirement is deleted. I'd like to see a Mapping that is allow to delete and you can select which direction that can occur.
Kenny Burnham
over 5 years ago
in Jira
2
Unlikely to implement
What is the challenge? Currently there is no automated way to visualize the tracked risks for reporting purposes (e.g. classical risk matrix) What is the impact? The user has to use multiple tools for reporting, instead of using Aha! as single sou...
Guest
7 months ago
in Reports
0
Future consideration
What is the challenge? A Slack Messages used to add comments to aha records or create ideas, by default, does not have context around who sent the message, when, what slack channel What is the impact? Either the context around the message is lost,...
Michael Gogos
7 months ago
in Slack
0
Future consideration
Right now workflow syncing, in our case between Requirements and Features, only occurs when the requirement is Updated. At times we are importing records that are already in an In Progress category and I'd like this to adjust the parent like it wo...
Fatimah Gorin
over 3 years ago
in
0
Future consideration