Azure DevOps Services and Server
Sort by:
Trending
Status:
Showing 108
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
1
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
13
VOTE
Allow additional Link Types in the 'Links to' field
Within AHA we are mapping
Releases -> ADO Release Work Item
Master Feature -> ADO Epics
Features -> ADO Features.
Master Features need to be located in the Release in which they complete. But Features (that contribute to this Master F...
2
Future consideration
12
VOTE
Allow Aha! user name to populate DevOps board user
When working with multiple users, we need to be able who created what, commented on or changed something. As of right now, the user name (Admin) of who configured the Integration (Azure DevOps Services) is the one that appears on every item in Dev...
3
Future consideration
8
VOTE
Support linking the Aha! URL field to the Azure DevOps Hyperlink field
Goal: We want to see in DevOps which Item it syncs with in Aha! Current set up: Aha! URL field linked to Hyperlink field in DevOps Challenge: We are using the hyperlink field to capture URLs to multiple sources. This is all being done in a single ...
2
Future consideration
19
VOTE
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
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
3
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
16
VOTE
Need full two way integration of a Story with VSTS
Right now you can push a Feature and associated stories to VSTS but if you delete a story in VSTS you have to manually delete in Aha. We need:
1) any story delete in VSTS to be automatically deleted in Aha
2) any story added in VSTS to a Feature...
1
Unlikely to implement
© 2024 Aha! Labs Inc.•All rights reserved