Managing a large pool of seats is time consuming. Instead of trimming a list we'd like to define who can use the paid seat and then pay for a concurrent limit. So say we have 250 people in portfolio management (which could be defined by HR job rol...
Keith Mantell
about 4 years ago
in
1
Unlikely to implement
Allow steps box in Story Board to grow so you can see the entire step
When you add a step to a user story map if the text expands beyond the visible part of the box it is not easy to see the entire step.
The box should grow in the same way as the feature box does.
Matt Garrett
over 5 years ago
in User story map
0
Unlikely to implement
Google Data Studio turns your data into informative dashboards and reports that are easy to read, easy to share, and fully customizable. Dashboarding allows you to tell great data stories to support better business decisions. I would like AHA to h...
Alex Horan
over 6 years ago
in Integrations / Wanted
0
Unlikely to implement
Auto-populate assigned Person from feature level to to both requirements and To-dos
When assigning a person to a “Feature”, we would like an update/option that also auto-populates that same person in the requirements and To-dos within that feature.
Guest
over 7 years ago
in Features
2
Unlikely to implement
Once requests are sent to JIRA there is no quick way to see the original Aha Idea source for the ticket. We would like to have the Idea ID exposed as a custom field so it can be mapped to JIRA. This will allow personnel working on the JIRA ticket ...
Guest
over 8 years ago
in Ideas
0
Unlikely to implement
Automatically create new copy features in other workspaces based on feature tags
Who would benefit? Any product owner that has multiple workspaces or multiple tiers of workspaces. What impact would it make? Reduce the amount of work by creating tickets once instead of copying and moving. Further, changes in the feature in one ...
Guest
about 1 year ago
in Features
1
Unlikely to implement
Ability to choose how each Aha Initiative/Feature/Requirement should be mapped to JIRA, as opposed to one mapping setting for an Aha product.
As a user, when creating a new Aha Initiative or Feature, I would like the ability to choose whether the Aha Initiative/Feature/Requirement should be mapped as a JIRA Epic, User Story, or Requirement, so that I can have more flexibility when creat...
Guest
almost 9 years ago
in
0
Unlikely to implement