Manual Sending of Requirements to integrated development tool
Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories. It will automatically s...
I R
almost 2 years ago
in Jira
2
Future consideration
What is the challenge? If a KB visitor reviews the documentation and is not able to find the answers they need, we want to provide them two options for getting further help: Submit a Salesforce case directly from the Knowledge Base Open up a chat ...
The ability to use an integration as a template prior to it's first time being enabled
What is the challenge? It's currently possible to use a disabled integration as a template, but before that is possible, you must first enable the integration and then disable it. What is the impact? This forces an extra step as users may want to ...
Stephanie Lechner
4 months ago
in Integrations
0
Future consideration
Who would benefit? Companies that leverage Viva Goals for OKR & initiative tracking in addition to Aha! Roadmaps What impact would it make? This would allow Product Managers and similar personas to continue the deep product-focused efforts in ...
David I.
11 months ago
in Integrations
2
Future consideration
Make the standard tags field mappable for requirements
Both epics and features have the standard tags field mappable when setting up an integration. Requirements now have a standard tags field added to the record but it is not available in the mappings. It currently requires a custom field be created ...
Justin Waldorf
over 2 years ago
in Integrations
3
Future consideration
Pendo is a great tool that our company uses to see how our clients interact with our product. I'd love to be able to pull in some of the analytics of product use into Aha. For example, how many users are using this new feature we launched, etc.
Guest
about 6 years ago
in Integrations
2
Unlikely to implement
The pivotal integration only allows for 2-way integration only if originally pushed from aha initially. Even then it's pretty limited to status and description.
If I create an 'feature' in aha which maps to an 'epic' in pivotal, and someone add...
Guest
about 10 years ago
in Pivotal Tracker
23
Will not implement