Skip to Main Content
ADD A NEW IDEA

Azure DevOps Services and Server

Showing 101 of 8645

DevOps Integration issue with multiple attachments default name Image.png

See the support request# #408720 for the integration error with for a work item with more than one attachment with same name. Resolution provided by Aha! support is to rename the image.png files differently so that DevOps accepts them. Can Aha! Im...
Sekhar Nallapaneni over 4 years ago in Azure DevOps Services and Server 0 Future consideration

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

ability to integrate idea information into Azure DevOps

We use the ideas portal to solicit new enhancements from our users and then link those ideas to features in our products. The problem is only our product management and dev management use Aha. our development team uses Microsoft DevOps to track th...
Joe Granville over 4 years ago in Azure DevOps Services and Server 0 Future consideration

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

Azure DevOps or JIRA integration : allow some way to automatically select which integration to use when more than one exists in a product

We usually map 1 Aha Product to 1 AzDo project, in which case everything is fine (except that everything ends up in the same Area Path). We can also easily map N Aha Products to 1 AzDo project, mapping each Product to an AzDo area path. But we cur...
Guillaume Metman almost 5 years ago in Azure DevOps Services and Server 0 Future consideration

Automatically create webhooks by default for Azure/TFS

No description provided
Guest almost 5 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 5 years ago in Azure DevOps Services and Server 0 Future consideration

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

Ability to set Aha field to a constant value as part of integration field mappings

My scenario is that I have each Aha product linked to multiple different projects in Team Foundation Server (TFS), and I want the features in Aha that come from TFS to have a field indicating what TFS project they came from. But I can’t find a way...
Tessa Adair about 5 years ago in Azure DevOps Services and Server 7 Future consideration

Converting requirements to features after integration

Converting a requirement to a feature will cause the record to lose some custom field information because features may not have the same custom fields. We can choose whether or not to proceed. There's no mention of integration to an external syste...
Tom Beck about 5 years ago in Azure DevOps Services and Server 1 Future consideration