Skip to Main Content
ADD A NEW IDEA

FILTER BY CATEGORY

Azure DevOps Services and Server

Showing 87

Allow a single Azure DevOps webhook to support updates across multiple Aha! integrations

With Jira, a single Aha! webhook added at the system level supports updates across all Aha! integrations. This makes scaling integrations simple as after the first setup, a user never has to add another webhook. With Azure DevOps (TFS), ea...
Guest over 3 years ago in Azure DevOps Services and Server 1 Future consideration

Iteration Path Integration with Aha & ADO

Though we have Iteration path integration between Aha and ADO. This is currently limited to show dynamic values for the integrations. Also the Iteration Path is based on the Area Path, the values of Iteration path cannot be filtered / shown releva...
Raghuraman Ragjendran 2 months ago in Azure DevOps Services and Server 1 Already exists

DevOps Integration: Sync "Task" Workitems with Aha's "To-Dos"

Currently, our main work in DevOps gets done within Task items which also have effort spent inside. These however are not a sync-option within the "To-Do" level of Aha!. The fields "Name, Description, Assigned to, Due Date (and maybe effort or oth...
Michael Scholze about 2 years ago in Azure DevOps Services and Server 1 Future consideration

Sync releases for Azure DevOps integration

Currently we cannot push work back from Azure to Aha correctly as the releases/Iterations do not sync which causes manual work to move a card to the correct Aha release once imported. Iterations can be nested in ADO, and when you try to send recor...
Ronnie Merkel over 2 years ago in Azure DevOps Services and Server 0 Future consideration

Keep features in sync when they cross areas in Azure DevOps

This is useful when you have your DevOps areas configured by team. Once the features are pushed from Aha! to DevOps and evaluated by the team they need to be moved into the area for the appropriate team. Any team can work on any feature based on a...
Deb Gay almost 4 years ago in Azure DevOps Services and Server 0 Future consideration

Fix critical Aha to VSTS Integration not syncing Feature Order

We are trying sync the Feature order from Aha to VSTS (never the other way around). Keeping the Features in VSTS in the same order in Aha is in our use case, critical to using the integration. The reason that it fails is because matching the Aha...
Guest about 4 years 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 over 1 year ago in Azure DevOps Services and Server 1 Future consideration

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

Limit workspace users choice to 1 user instead of multiple (like the Assigned to) field

I need to add the workspace users as a custom field in my template and currently it doesn't limit to just one user, it allows multiple users which I cannot have. Can we have an option to make it a single choice only. in the attached graphic is the...
Stacy Monnahan 7 months 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 about 3 years ago in Azure DevOps Services and Server 3 Future consideration