Reference capacity planning fields in calculated column equations
Currently the capacity planning fields are not available to use in the Custom Equation builder. It would be great if we could use the fields to perform calculations in list/pivot reports.
An example use case is to calculate the risk of completion ...
Madeleine Black
over 5 years ago
in Reports
3
Shipped
Include the new Research tab in Ideas - not only in features
The new research tab in features is really valuable in the idea stage. Early on you are researching the idea business case and the need for the research templates at this stage is important even before you descided to priorotize and convert it to ...
Edit the documents in a KB outside of the existing parent line
What is the challenge? Currently when you create a knowledge base , you select the root document to publish. Any child notes nested underneath it are included as well. There is a need to edit the documents in a KB in a broader way. How would you s...
We would like the ability to have new records created in JIRA/Rally automatically import into Aha!
Currently, they have to be accepted in Aha! prior to import. This causes an extra step in our workflow we do not wish to have to go through each time.
Danny Archer
about 7 years ago
in Integrations
7
Shipped
Currently the spam filter is only available in public portals. However in some cases, such as when SSO is enabled for users of an app, where filtering for spam is still necessary.
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
about 7 years ago
in Strategy
12
Shipped
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.
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.