It would be helpful if we had the ability to copy a requirement to the same feature. We use requirements as product backlog items. Sometimes they are too big. It would be useful to be able to copy a requirement as the first step in splitting it.
Add Competitors, Business Model, Personas and Vision to be terms which can be renamed under 'Terminology'.
Competitors is not hugely relevant for the large areas of the product organisation currently working with. However, being able to re-use competitors and it's charting capability to represent some strategically important to them is. For example, it...
Project Parker
over 6 years ago
in Strategy
12
Shipped
Ability to define filters within an Aha! dashboard
The new Aha! dashboards are great! It would be nice to be able to filter the data contained within those dashboards. For example: I have a dashboard of portfolio initiatives across the organization. Each portfolio leader will want to zoom in and s...
Mark Eaves
almost 4 years ago
in Reports
4
Shipped
Link existing GitHub issues with a new Aha! Feature
The current Aha! - GitHub integration lets you sync features to GitHub issues. This won't work in the opposite way. However, It'd be nice to have an editable field to reflect that the Aha! feature is linked to a GitHub issue.
When a custom table field is used in a key result, cannot report on the key result's custom table
What is the challenge? I am using a custom table on key results to report on quarterly updates to the key result. When I go to build a report, the custom table does not show as a record related to my key result record. What is the impact? Limits p...
As a product manager who manages multiple products and has a development team working with multiple productsI would like a straightforward way to prioritize features across productsSo that I can communicate to my developers what our highest priori...
Daniel Schwent
about 5 years ago
in Features
3
Shipped
We often use various lists and reports. Unfortunately, their utility is limited due to the fact that filters are only inclusive. We'd like to see filters built with the ability to exclude certain things (i.e. tags, keywords, dates, etc)
Map Jira's "Won't Fix" resolution status to Aha!s "Won't implement" status
When the Jira workflow is set up to "Close" a ticket with the resolution status of "won't fix," there currently is now way to map that against the Aha workflow.
It would be great to also access the Resolution status from Jira to handle this c...