Skip to Main Content
ADD A NEW IDEA

Azure DevOps Services and Server

Showing 101 of 8637

Add the work item Id to the Import new records dialog

It would be useful to show the work item Id in the list of records available to import as it's easier to search for a specific identifier than a name
David Beaumier almost 4 years ago in Azure DevOps Services and Server 5 Future consideration

Bulk Delete for files , and don't default to ADO integration - Attachments

Whoops. I accidentally set up the ADO integration to include attachments, and now I've got hundreds of ADO development files in my beautiful AHA portal "Workspace Files" section. I've now switched off the attachment synchronization, but left with ...
Guest almost 4 years ago in Azure DevOps Services and Server 0 Future consideration

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.
Guest almost 4 years ago in Azure DevOps Services and Server 0 Future consideration

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 ...
Ronnie Merkel almost 4 years ago in Azure DevOps Services and Server 2 Future consideration

Ability to execute a AzureDevOps query and display results in charts on Aha Dashboard

For the teams who uses AzureDevOps as ALM tool , It would be great flexibility to view a snapshot of the query results on the Aha dashboard. It does not need to be sync but can be pulled async.
Guest almost 4 years ago in Azure DevOps Services and Server 0 Future consideration

Allow TFS integration to map bidirectionally for fields that are not in a built-in System.State.

Currently, the TFS integration does not support mapping arbitrary string fields to the Aha! workflow status field in a bi-directional way. Only the built-in System.State field in TFS can be mapped bidirectionally.
Guest almost 4 years ago in Azure DevOps Services and Server 2 Future consideration

Add 2-way integration mapping for release start and end dates

Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release. Now that this date is set manually, it should be poss...
Austin Merritt about 4 years ago in Azure DevOps Services and Server  / Integrations / Jira / Rally 2 Future consideration

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...
Guest over 4 years ago in Azure DevOps Services and Server 3 Future consideration

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 M...
Guest over 4 years ago in Azure DevOps Services and Server 2 Future consideration

Allow parent mapping of releases to initiatives

In ADO we use assign our epics as children of themes. In AHA we map themes to initiatives and epics to releases but in the integration configuration we cannot set the parent mapping.
Joe Granville over 4 years ago in Azure DevOps Services and Server 0 Future consideration