All ideas
Sort by:
Trending
Status:
Shipped
Showing 2470
38
VOTE
Change the Notebook web page transition
The fancy, flippy dippy transition in the Notebook web pages is more than annoying . Can you please do one of the following?
1. Make it a simple scroll so the user does not have to jump pages. If there are multiple pages, the user has to remember ...
3
Shipped
5
VOTE
Allow reporting to add the goal field on the initiative and initiative roll-up records (without related record)
When creating list/pivot reports, the goal field is available on the feature record. However, the goal field is not available for reporting on the initiative record or roll-up initiative records. It would be helpful to be able to see the goal fiel...
0
Shipped
34
VOTE
Add multiple idea forms for same product
As a product manager, I must have the ability to accept enhancement requests from different stakeholders who have different types of information to provide, so that I can collect the right type of information needed to address the requirement.
We ...
7
Shipped
42
VOTE
TFS (a.k.a. VSO) Automatically create new stories in TFS as requirements in Aha! when stories are created under a linked feature.
If a feature has been sent to TFS as a feature and requirements as stories, when I create a new story under the linked feature I would like it to be automatically created in Aha! as a requirement.
2
Shipped
2
VOTE
Include Create Object Option under related tab on Phases
What is the challenge? Within the Aha! UI, all objects (Features, Epics, etc) include the ability to link to an existing object, or create a new object from the related tab. Except for Phases, which do not offer this option. What is the impact? Th...
0
Shipped
2
VOTE
Create automations based on estimate fields
What is the challenge? I cannot create an automation when an estimate field is updated. I have a tag that lets my dev lead know when a feature needs an initial estimate. When the initial estimate on a feature is updated, I'd like to remove the tag...
0
Shipped
42
VOTE
41
VOTE
34
VOTE
29
VOTE
Allow a Feature (epic) in Aha! to have Requirements (stories) that live in a different Jira project
The use case is that we create features in Aha! and sync them to Jira as epics. The development team will then break the epics down further into stories in the appropriate Jira projects for the teams that need to work on them. In Jira, these stori...
3
Shipped
© 2024 Aha! Labs Inc.•All rights reserved