Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Azure DevOps Services and Server

Showing 120

Map VSTS/TFS picklist custom fields to Aha! choice list fields

VSTS/TFS picklist custom fields are treated as strings and cannot support option mappings. Mapping a picklist field to an Aha! choice list field should provide the option to click Configure and map the choices.
Tessa Adair over 6 years ago in Azure DevOps Services and Server 9 Future consideration

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 almost 5 years ago in Azure DevOps Services and Server 1 Future consideration

Add support to map Azure Boolean Fields to Aha

This request is to support the mapping of ADO boolean fields to Aha predefined droplist and tag fields. Currently, Azure DevOps Boolean fields (true/false) cannot be mapped to Aha fields. Rather, in ADO, you need to create a field as a picklist in...
Jerrold Emery over 3 years ago in Azure DevOps Services and Server 0 Future consideration

Add Markdown support for ADO integration

What is the challenge? Markdown editing has been added in Azure DevOps for rich text fields. However, when the data is migrated to Aha, it's stored as raw Markdown rather than displaying as formatted text. What is the impact? Makes integra...
Carah C 3 months ago in Azure DevOps Services and Server 0 Future consideration

Allow use of Mapped fields template with one field difference for each integration

What is the challenge? Can't use Mapping Integration template. Have to update multiple integration for every mapping change since one has to be different. What is the impact? Would save a ton of time for our team. Describe your idea We have around...
Alex Berestenko 9 months ago in Azure DevOps Services and Server 0 Future consideration

Enable Roll-up Initiative link in the standard Azure DevOps Services integration

What is the challenge? Unable to integrate multi-layered strategic initiatives from Aha to ADO What is the impact? Manual updates to keep information in sync, prone to errors. Question whether we will continue to utilize Aha or work direct...
Ryan Bradley 3 months ago in Azure DevOps Services and Server 0 Future consideration

Import items even if a parent is not available due to security restrictions

What is the challenge? Some of our work items (e.g. a feature) in ADO are linked to security related parents (e.g. an epic) in ADO. We are not able to access the parent work item due to these security settings. However we would like to see the fea...
Tobias Getz 7 months ago in Azure DevOps Services and Server 0 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 about 5 years ago in Azure DevOps Services and Server 0 Future consideration

Handle multi-select fields in ADO integration

What is the challenge? Running into an issue where multi-select from Aha can't flow over to ADO multi-select field. Only first value flows over from Aha. What is the impact? Can't use multi-select field in ADO properly. Describe your idea Allow fo...
Alex Berestenko 12 months 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 R...
Guest almost 7 years ago in Azure DevOps Services and Server 2 Future consideration