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...
Automatically update features end date by the end date of the release
If the feature will be moved from one release to another release, end date of the feature should be automatically updated by the end date of new release.
Guest
over 5 years ago
in Features
1
Future consideration
Automation for epics/features at the parent line level
As a portfolio manager, I want to create a single rule for epics/features for all workspaces in a parent line. Right now I have to recreate these individually at the workspace level. Part of the problem is the amount of time it takes to create eac...
Guest
almost 5 years ago
in Automations
0
Future consideration
What is the challenge? Conceptually, a to-do on a feature having a record link is no different from a requirement on a feature having a record link. The to-do could be blocked by or block any other record, it could depend on or be depended on. Sev...
Guest
over 1 year ago
in To-dos
0
Future consideration
When sending a Feature to JIRA, automatically move the new JIRA epic/story into the JIRA project's Backlog
When we sync Aha! Features into JIRA, we're ready to begin planning sprints that will include the resulting JIRA epics/stories. Extend the JIRA integration so when new epics/stories are created from Aha!, automatically move them into the JIRA proj...
Comment fields: Any one with contributor status should be able to update the comments field and should be ordered newest to oldest
The comments field is used by several people to comment on status, updates, questions etc. Contributors should be able to add update comments started by other people to keep the thought thread together. Also, they should have a sort order provided...
Hide initiatives of specific status' from Features
When creating initiatives there are times when they have not been approved or started. When a user is looking at a feature, I don't want them to be able to select initiatives that are not fully baked. If the status category of an initiative is eit...
Guest
about 8 years ago
in Strategy
0
Future consideration
What is the challenge? Referring to written text as well as attachments remains with the Idea. What is the impact? Excessive clicking and thought tracking Describe your idea When an Idea is promoted to Feature, all input text will be copied to the...
Guest
10 months ago
in Features
0
Future consideration
Sync Aha! feature date range to Jira associated sprint date range
What is the challenge? The product team manages the roadmap in Aha! and the dev team manages the development in Jira. Stories sometimes slide from one sprint to another and the date range of the release is not up to date with the reality What is t...
Guest
10 months ago
in Jira
0
Future consideration
Include Feature Template when creating Features from Story Map
The default feature template appears when adding a new feature from everywhere in aha except when creating features from the story map view. The description appears blank. This is a problem because we are transferring our story maps into aha and l...
Guest
over 6 years ago
in Features
3
Future consideration
"Make everything OK" button on feature that triggers insert/update/delete/move JIRA->AHA
Hello, it would be very helpful if in scenario, where aha records are linked to dev tool records (e.g. JIRA), there would be a possibility to trigger full record update for a single record. Example: integrations config: Features linked to Epics in...
Guest
over 6 years ago
in Jira
10
Future consideration