Azure DevOps Services and Server
Sort by:
Trending
Status:
Showing 108
2
VOTE
Include author of comment from Azure DevOps when saving to Aha
We use the Aha <-> Azure DevOps integration. Comments from Aha include the author when synced to AzDO (Comment added by <user> in Aha! - View). The reverse is not true. Comments made in AzDO that come to Aha do not say the other, just ...
0
Future consideration
5
VOTE
Sync sprints between requirements in Aha! and equivalent (e.g. PBIs) in Azure DevOps
Our development team manages PBIs within sprints. Currently you can map a custom sprint field for features in Aha! to DevOps, but not requirements. Ideally, we would be able to sync sprints for requirements/PBIs, as that would be more useful than ...
0
Future consideration
5
VOTE
Comment Synching to Azure DevOps
As an Aha user, when I create a Requirement with a Comment which is mapped to Azure DevOps I need the initial Comment to synch to Azure and not just subsequent Comments Working with offshore teams, and not able to speak to them during off hours, w...
0
Already exists
4
VOTE
Allow two-way integration for picklist fields in Azure DevOps when using the XML process model
This idea is a variation on https://big.ideas.aha.io/ideas/AFME-I-2, but the general use case is the same. I've been asked by Aha support to make a separate idea specifically for those using the XML process model, since this has supposedly been fi...
0
Future consideration
7
VOTE
Nested Iteration Paths with VSO / Visual studio team services integration
We have the same VSO project for many products in Aha. We would like the ability to have child iterations for releases so we can group them together in our queries. Current integration only allows us to go 1 level deep in the iteration path.
Our...
0
Already exists
2
VOTE
Aha! Releases Should Honor ADO Area by Default
I am unsure why this feature was designed this way; However, when creating and pushing a release from Aha! to ADO, it should honor the area path set up in the Aha! to ADO integration. Furthermore, when linking to an existing iteration in ADO, the ...
0
Future consideration
2
VOTE
Links to Azure DevOps items should be dynamically created based on integration settings
We underwent a branding change and had to update our Azure subdomain and after updating all our workspace integrations in Aha!, the hyperlinks (Azure DevOps Services url) were still pointing to the old subdomain and there is no way to refresh them...
0
Future consideration
5
VOTE
Ability to customize the Import Import New Records dialog box and functionality
It would be very helpful to be able to customize and configure the Import New Records dialog box. Specifically I would like to be able to select additional/different information about each record (i.e. Azure DevOps work item #, State, Iteration) i...
0
Future consideration
4
VOTE
Import of time tracker data from 7pace Timetracker to Aha!
7pace timetracker is an integrated time mamagement solution for teams using DevOps. We would like to pull time tracker data into Aha! through our DevOps integration to ensure Aha! has a clear view of the time spent on Features.
1
Future consideration
3
VOTE
Allow mapping Release as a field on Requirements in Azure DevOps integration
Due to our iterations setup in Azure DevOps (ADO) we do not currently map Releases as a record. We are sending this instead as a field on the Epic and Feature records to a custom field in ADO. We would like to do the same on Requirements but it is...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved