PINNED
Chrome extension to capture feedback from anywhere
What is the challenge? We work in many applications and Aha! can not build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? This res...
Definitions for terms/concepts between product lines often vary. It would be great to be able to create a glossary/ubiquitous language archive where definitions can be linked to product lines or different products. This will help developers use bu...
Guest
about 7 years ago
in Account settings
2
Unlikely to implement
We like to represent a release with release timing ambiguity with the estimated release function (Q2 2022), but are looking for a way to represent this visually. One option could be to represent the estimated timeframe across the estimated frame t...
Guest
over 3 years ago
in Roadmaps
0
Future consideration
Auto-Update Release Phases in Template to New Release
Once a template with release phases is created, the release phases in that template will automatically adjust their dates to fit within the date range of a release using the template.
Guest
over 3 years ago
in Releases
2
Unlikely to implement
Add ability to extract list of field names and API keys via API
It would be helpful to be able to extract, via the API, a list of field names mapped to their API keys. This would aid users in uploading information to our workspace without them needing to know what the API relationships are. i.e. the field in t...
When creating a new Feature in Aha! and pushing the data to Jira: Aha! should have a way to handle sending data to Jira fields which are: a) required b) Autocomplete Renderer so the Epic can be created and not rejected by Jira
I created a new feature in Aha! When I attempted to send the changes from Aha! to Jira, expecting a new Epic to be created in Jira, I got the following error: The following required fields could not be set on the epic: Fix Version/s. Please check ...
Guest
about 7 years ago
in Features
8
Already exists
when a requirement is added as a dependency to a feature, it should show up as a requirement
We often want to link one requirement to multiple features by making a requirement dependent on multiple features. However, when we make this link we are only able to see the requirement under the related to tab
Guest
over 3 years ago
in Dependencies
0
Unlikely to implement
With the creation of Note templates, it would be nice to be able to apply that template to all pages within that note hierarchy instead of recreating the page - copy and pasting content into that new page.
Marina Reyna
over 3 years ago
in Notes
3
Future consideration