All ideas
Sort by:
Trending
Status:
Showing 9041
5
VOTE
When sending a Release to Pivotal Tracker, items are added to the backlog in reverse order
Items are prioritized in Aha's release area by the Product Manager. When sending the release to Pivotal Tracker, the Stories that appear in PT are in reverse order, meaning the engineering team must spend time comparing lists to fix the order.
I e...
1
Will not implement
1
VOTE
Allow link of a requirement to a release (sprint)
We have features that are mapped to a specific sprint, but within that feature, we have requirements (user stories) that could be mapped to two different sprints. The assumption with Aha! is that a feature would be completed in one sprint, which i...
0
Future consideration
1
VOTE
Promote Notes OR To Dos to Feature
We are trying to bring our Cross functional partners into Aha and would like a way to easily request work from them. We had been copying our Feature and assigning the UX-specific Feature to them. This allows for the details from the Product Develo...
0
Future consideration
2
VOTE
4
VOTE
History of items created via integration
In Jira integration 2.0, there's no link or reference to the items created by the integration once you approve them.
A modal notification like you currently use would work at a one-by-one level. If that makes sense.
Even better would be a tab in ...
1
Future consideration
2
VOTE
3
VOTE
Allow customization/formatting in the feature or initiative detail record
It would improve the user experience if in the feature/initiative record we could: 1) have the ability to hide from view components that are not being used (such as features and releases), otherwise the detail record can be very long and "messy" f...
0
Unlikely to implement
3
VOTE
Ability to push updates to integration that has come from another integration
Long story short.
Our company uses Jira for Customer Service ticketing system and Development team uses Azure DevOps. In between we have Aha! where all features and roadmap is managed. When we take bug fix or improvement task from Customer Service...
0
Future consideration
4
VOTE
Integrations 2.0: Allow Master Feature relationship for Requirements
I can create a relationship for Releases at the requirement level even though requirements do not inherently have a release field, this appears to be derived from the feature. I should also be able to create a relationship to the Master Feature in...
0
Future consideration
1
VOTE
© 2024 Aha! Labs Inc.•All rights reserved