Skip to Main Content
ADD A NEW IDEA

Azure DevOps Services and Server

Showing 104 of 8810

Include Attachment for Release In Integration

What is the challenge? For Releases Attachments are not supported in Integration Set Up How would you solve it? Manually Project Managers are uploading in Devops What impact would it make? It will reduce so much of manual work
Guest 4 months ago in Azure DevOps Services and Server 0 Future consideration

Include Attachment for Release In Integration

What is the challenge? For Releases Attachments are not supported in Integration Set Up How would you solve it? Manually Project Managers are uploading in Devops What impact would it make? It will reduce so much of manual work
Guest 4 months ago in Azure DevOps Services and Server 0 Future consideration

Include Area Path in VSTS Integration

I really like the VSTS integration 2.0, however could you add Area Path to the list of available fields that can be mapped to. This would be useful as in VSTS we use Area Path to note which dev team has picked up a feature and it would be great to...
Guest about 6 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 almost 5 years ago in Azure DevOps Services and Server 2 Future consideration

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...
Bryan McElhinney almost 2 years ago in Azure DevOps Services and Server 0 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

Sync the change of parent link made in Aha! across 2 Azure DevOps integrations

Who would benefit? Customers with multiple integrations set up to ADO who are wanting to move features to different Epics as their plans change. What impact would it make? How should it work? The parent/child relationship should be tracked across ...
Stuart Blair 5 months ago in Azure DevOps Services and Server 0 Future consideration

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

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 ...
Euan Callow about 3 years ago in Azure DevOps Services and Server 2 Future consideration

Warn user of integration on epic deletion

Who would benefit? Integration users What impact would it make? How should it work? When you delete a feature which is linked to a dev system you get a warning (attached). When you delete an epic, you do not get a consitent warning. This suggestio...
Tom Bailey 9 months ago in Azure DevOps Services and Server 0 Future consideration