Azure DevOps Services and Server
Sort by:
Trending
Status:
Showing 91
4
VOTE
Update records selectively
The "Update Records" feature currently updates all integrated records defined in the Azure DevOps integration. This could take quite some time if the number of records is high. Sometimes you only want to upgrade on a particular record type because...
0
Future consideration
1
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...
0
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
2
VOTE
Fix sync of grid style between Aha and DevOps
We often create features in Aha and sync them into DevOps for the Dev Team. Our dev team then creates the user stories and syncs those back to Aha. They use a small grid in their user story template in DevOps. When it syncs back, that grid is oddl...
0
Future consideration
11
VOTE
Allow VSO integrations to work with multiple Aha Products represented in a single VSO Project
Some customers have specified that they maintain a single VSO Project, but represent a number of products beneath it. The way to handle that now in Aha is to set up a web-hook for each product in Aha, and then create a subscription in VSO that fil...
1
Unlikely to implement
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
4
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
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
3
VOTE
4
VOTE
Azure DevOps integration support for designating default Iteration as backlog
Currently the Azure DevOps Services integration supports configuration of the project and the project area. All work items go to the root project iteration level. However, multiple teams may work in a single project and have a different iteration ...
2
Future consideration