ADD A NEW IDEA

FILTER BY CATEGORY

Azure DevOps Services and Server

Showing 42 of 6678

Inherit the hierarchy of the area paths from Azure Dev Ops

When integrating with Azure Dev Ops, the area paths should inherit the same hierarchy when represented in Aha. For example, hierarchy in Dev Ops could be: Company/Company /Functional AreaCompany/Functional Area/TeamThe Aha Azure devops integration...
Guest 3 months ago in Azure DevOps Services and Server 5 Future consideration

Add Automation Rule Action to Trigger Link/Send to ADO Integration

When a Release has been agreed on and finalised you want to send the items through to ADO for developers to start work on then based on a Release Status or individual Feature Status (or other criteria) to Send the Features through to ADO based on ...
Guest about 2 months ago in Azure DevOps Services and Server 0 Future consideration

Configurable destination of imported features

As a product manager, I should have control over the destination of where imported features and epics go so that they are in the release or parking lot where they belong. Today, the destination of imported items seems almost up to chance although...
Tom Beck over 2 years ago in Azure DevOps Services and Server 8 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 8 months ago in Azure DevOps Services and Server  / Rally / Jira / Integrations 0 Future consideration

DevOps Integration -- Support rendering of images embedded in description field

Currently when you import from Azure DevOps, if you have images embedded into the description field, they come over as a link in the Aha! description field, e.g. imagename.png. It would be great if they would render in Aha! like they do in DevOps...
Mike Maylone 4 months ago in Azure DevOps Services and Server 0 Future consideration

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 ca...
Kalyndra Craven 29 days ago in Azure DevOps Services and Server 0 Future consideration

Sync sprints between requirements in Aha! and equivalent (e.g. PBIs) in Azure DevOps

Our development team manages PBIs within sprints. Currently you can map a custom sprint field for features in Aha! to DevOps, but not requirements. Ideally, we would be able to sync sprints for requirements/PBIs, as that would be more useful tha...
Mike Maylone 3 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 D...
John Doe 10 months ago in Azure DevOps Services and Server 3 Future consideration

Integration to Azure DevOps for teams capacity planning

We would like to use Points based capacity planning but it needs to be integrated with (in our case) Azure DevOps which is where the team is committed to and working on work. All of our Features and Master Features (Epics) in Aha are calculated b...
Heath McCarthy 3 months ago in Azure DevOps Services and Server 0 Future consideration

Configurable unit of time for Estimation field

We're using Aha with Azure DevOps integration. We’ve mapped the Estimate field in Aha with an estimate field in Azure DevOps. Our estimation process is basically as follows: * Product Manager creates Feature in Aha * Product Manager send RFC in...
Guest over 1 year ago in Azure DevOps Services and Server 4 Future consideration