Skip to Main Content
ADD A NEW IDEA

My ideas: Azure DevOps Services and Server

Showing 103 of 8728

Fix sync of grid style between Aha and DevOps

We often create features in Aha and sync them into DevOps for the Dev Team. Our dev team then creates the user stories and syncs those back to Aha. They use a small grid in their user story template in DevOps. When it syncs back, that grid is oddl...
Guest over 2 years ago in Azure DevOps Services and Server 0 Future consideration

Provide the ability to map the Release field from a Feature or Epic to an external system such as ADO

Given that AHA is all about releases and ADO is all about time lines, the concept of a Release in AHA is quite different than what exist in ADO - yet there is a Target Release field in ADO as well as in the Feature of AHA - please can this be expo...
Dirk K about 3 years ago in Azure DevOps Services and Server 1 Future consideration

Configure iterations based on phases in DevOps

We're using multiple layers of iterations within Azure DevOps. So a Release consists of multiple sprints. I would like to be able to map not only releases to iterations, but also phases to iterations. That way I can use Aha! as a single point of e...
Carlo Bril over 3 years ago in Azure DevOps Services and Server 0 Future consideration

Custom Record Type, Made Up Entirely Of Custom Fields

We have some customer systems that we need to sync data back from. These are generally tasks that are created in systems we integrate with (specifically Azure Dev Ops, with the Task record). We are an outsourced product management company, so we h...
Guest over 3 years ago in Azure DevOps Services and Server 0 Future consideration

Allow integration with custom work item types

Sometime companies use customized templates with custom work item types. Currently the ADO integration only supports integration with the standard types like "initiatives", "features", "Requirements". Our template supports a custom type called "PI...
Guest over 3 years ago in Azure DevOps Services and Server 3 Already exists

Allow Integration variable on Create Record layout

Currently when creating a feature, I have to create the feature and then manually send the integration to ADO. I want to have a variable on the Create Record Layout screen to be able to choose this option when creating the feature. This way I can ...
Kalyndra Craven over 3 years ago in Azure DevOps Services and Server 0 Future consideration

Add the work item Id to the Import new records dialog

It would be useful to show the work item Id in the list of records available to import as it's easier to search for a specific identifier than a name
David Beaumier almost 4 years ago in Azure DevOps Services and Server 5 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 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

Integration by status

I'm not sure how much demand there would be for this, but I've had a need a few times for it so I'm going to suggest it. I would like to be able to limit automatic integration of new requirements if they are in a certain state, such as New. If a f...
Tom Beck over 5 years ago in Azure DevOps Services and Server 0 Future consideration