All ideas
Sort by:
Trending
Filter by:
Status
Showing 8737 of 8737
18
VOTE
When an integration update comes from JIRA, it would be useful to see the "integration" completed the update in history instead of the callback user.
The callback user usually is not the one making the update in JIRA. It is almost 100% someone else on the technology side and not the product team. JIRA indicates that the integration updated the JIRA issue. It would be nice if Aha did the same.
5
Future consideration
1
VOTE
Force rank epics across multiple releases
Who would benefit? Everyone What impact would it make? It would allow proper prioritization for roadmap grooming How should it work? It should allow you to categorize master features in some way not connected to releases, and assign the a rank tha...
0
Already exists
1
VOTE
Streamlined Aha Email Notification to Browser Experience
Who would benefit? Product Managers that receive email notifications that someone has commented on an idea they are working on or if they have been tagged on an idea. What impact would it make? It would reduce the number of clicks required to acti...
1
Already exists
1
VOTE
Select ascending/descending sort order in Now/Next/Later roadmap columns
Who would benefit? Users who use date ranges in their N/N/L roadmaps What impact would it make? Clarify sequencing of work within each column, informing viewers what is coming next How should it work? When cards are sorted by date in any of the co...
0
Future consideration
1
VOTE
Sync the change of parent link made in Aha! across 2 Azure DevOps integrations
Who would benefit? Customers with multiple integrations set up to ADO who are wanting to move features to different Epics as their plans change. What impact would it make? How should it work? The parent/child relationship should be tracked across ...
0
Future consideration
1
VOTE
Want Customize List Report column name in API Response
Who would benefit? All users who are using List report API. What impact would it make? We will able to identify columns in API Response. How should it work? when we changed the Column name of list report , Currently that changed column name is not...
0
Future consideration
5
VOTE
Project level automation with Jira
Requesting a change to Aha! Jira integration to allow for project level automation. Project level webhooks send payloads differently than system level payloads. If support for project level webhook payloads were added, we could enable multitudes o...
0
Future consideration
12
VOTE
Configure AHA! to support GSuite - sheets, slides, docs, etc.
We are a company that uses GSuite, this would allow us to pull data into our collaborative space and manipulate reports to personalize further than what AHA! current allows. Currently the inability to use AHA with GSuite causes delays and setbacks...
0
Future consideration
12
VOTE
Efficient removal of scenarios from capacity planning for teams
After having completed planning with the use of various scenarios (with capacity planning for teams), I would have narrowed down my optimal scenario and would want to remove or archive scenarios that are no longer needed. Currently to delete a sce...
0
Future consideration
29
VOTE
Adding Feature Workflows for Feature Types
Aha! allows you to create feature workflows for a product, but not for a feature type. It would be helpful to have product workflows applicable beyond the product - allowing users to customize completion workflows per feature type.
Let's look at...
4
Future consideration