Azure DevOps Services and Server
Sort by:
Trending
Status:
Future consideration
Showing 99
6
VOTE
Filter capabilities on the Integration Update Import screen
As one Product Owner of a very large product that has a lot of product owners, I would like more filter capabilities on the Integration Updates import screen so that I can only see items that pertain to my portion of the backlog. This request is s...
1
Future consideration
1
VOTE
Import items even if a parent is not available due to security restrictions
What is the challenge? Some of our work items (e.g. a feature) in ADO are linked to security related parents (e.g. an epic) in ADO. We are not able to access the parent work item due to these security settings. However we would like to see the fea...
0
Future consideration
2
VOTE
Support configuring capacity units of time for ADO server integrations
What is the challenge? Currently the "Configure" option to select units of time to send estimates to ADO is only avaiable on the ADO Services integration and is not available for users using the Server integrations. What is the impact? Users are u...
0
Future consideration
12
VOTE
Ability to set Aha field to a constant value as part of integration field mappings
My scenario is that I have each Aha product linked to multiple different projects in Team Foundation Server (TFS), and I want the features in Aha that come from TFS to have a field indicating what TFS project they came from. But I can’t find a way...
7
Future consideration
4
VOTE
Ability to refresh data from the development tool for a single Aha record
Sometimes I'd just like to fix a record or two that have gotten out of sync. When I click on the Integrations menu for a particular feature, I have the option to resend all fields to my development tool (Aha -> ADO), or, to delete the link. IDE...
0
Future consideration
5
VOTE
New features created via an ADO integration are assigned to the parent epic release by default
Key problem: the "Parent" field in ADO can contain only one value. In ADO, a feature is automatically associated to the same theme as its' parent epic, but in Aha! this is not the case. So when features import, we associate them with the correct p...
0
Future consideration
12
VOTE
Control how Estimates are converted and sent to TFS/VSTS
The default behaviour of how the TFS/VSTS integration sends time Estimates in minutes is very limiting.
I don't know any agile team that would be estimating Features or Requirements down to minutes, so it doesn't make sense for the integration to ...
1
Future consideration
3
VOTE
Show name of user whose token is being used in ADO integration
Who would benefit? Admins of accounts with ADO integrations What impact would it make? When an ADO integration is created, a user with the correct permissions must enter their token to authenticate the integration. However, the token owner's name ...
0
Future consideration
8
VOTE
Integration to Azure DevOps for teams capacity planning
We would like to use Points based capacity planning but it needs to be integrated with (in our case) Azure DevOps which is where the team is committed to and working on work. All of our Features and Master Features (Epics) in Aha are calculated ba...
2
Future consideration
4
VOTE
Update the Feature % Complete field based on User Stories of the DevOps Feature
Update the Feature % Complete field based on User Stories of the DevOps Feature that is linked to the Aha Feature. The Software Product Plan does just that! In DevOps, this information is a calculated field, which can be easily configured in Board...
2
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved