ADD A NEW IDEA

FILTER BY CATEGORY

Azure DevOps Services and Server

Showing 95

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 over 1 year 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 possi...
Austin Merritt over 1 year ago in Azure DevOps Services and Server  / Rally / Jira / Integrations 1 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 D...
Guest over 1 year 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 ...
Guest almost 2 years ago in Azure DevOps Services and Server 1 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 almost 2 years ago in Azure DevOps Services and Server 0 Future consideration

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

Support tables in devops descriptions

Aha! has nicely support tables. When syncing with azure devops it would be nice if they had a border. a b c d looks something like the attachment. Copying from other editors looks correct.
Guest almost 2 years ago in Azure DevOps Services and Server 0 Shipped

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