All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5693
8
VOTE
Roadmap history: Show when delivery risk flags were raised or removed
Who would benefit? Product teams tracking delivery risks What impact would it make? Teams often need to understand not just what records are currently at risk, but when the risk was raised (and by whom, when relevant) and when the risk was mitigat...
0
Future consideration
75
VOTE
Integration: Cisco Webex Teams
It would be great if there is native integration of Aha.io with a Cisco Webex Teams bot much like the current Slack bot that is already available on Aha. Lots of users don't use email now and Teams is a great way to get notifications of posts and ...
2
Future consideration
3
VOTE
Configuration to limit notifications from requirements of features being watched
What is the challenge? Whenever a user watches a feature, they automatically receive notifications for all of the requirements that are created and updated on the feature. What is the impact? Users would be able to limit the amount of unnecessary ...
1
Future consideration
3
VOTE
111
VOTE
17
VOTE
Manual Sending of Requirements to integrated development tool
Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories. It will automatically s...
2
Future consideration
41
VOTE
Customize Default Fields on Records - Renaming and Adding Descriptions
This applies to all records with required default fields, not just Features: I would like to be able to customize fields that are default/'out of the box' fields on records. Specifically, I would like to be able to rename and add descriptions (hov...
10
Future consideration
2
VOTE
Bi-directional support for Area Level fields in ADO integration
What is the challenge? Currently we offer Area Level fields in our ADO integration for each Area Level. This allows us to receive the unique Area Level from ADO, but currently updates in Aha! do not change the Area Level back in ADO despite the se...
0
Future consideration
3
VOTE
Restrict ability to open or close sprints
What is the challenge? On some teams, only certain team members are allowed to start or close a sprint. Currently anyone with contributor access can open or close a sprint. What is the impact? Sprints are open or closed in error. Describe your ide...
1
Future consideration
10
VOTE
Allow Release Date (internal) and Release End date (date range) to sync
Who would benefit? The Release date (internal) drives many of the OOTB reporting functionality in Aha! so it must be maintained and accurate for reporting to be accurate. For many teams, the end date of the release and the Release date (internal) ...
1
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved