Azure DevOps Services and Server

We are currently using Aha! Roadmaps and asking for consideration of implementing OAuth authentication when setting up the integration to Azure DevOps Services. With Microsoft making the push towards strengthening their customers security posture,...

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...

Who would benefit? Integration users What impact would it make? How should it work? When you delete a feature which is linked to a dev system you get a warning (attached). When you delete an epic, you do not get a consitent warning. This suggestio...

We have features that are mapped to a specific sprint, but within that feature, we have requirements (user stories) that could be mapped to two different sprints. The assumption with Aha! is that a feature would be completed in one sprint, which i...

I am unsure why this feature was designed this way; However, when creating and pushing a release from Aha! to ADO, it should honor the area path set up in the Aha! to ADO integration. Furthermore, when linking to an existing iteration in ADO, the ...

We underwent a branding change and had to update our Azure subdomain and after updating all our workspace integrations in Aha!, the hyperlinks (Azure DevOps Services url) were still pointing to the old subdomain and there is no way to refresh them...

I need to add the workspace users as a custom field in my template and currently it doesn't limit to just one user, it allows multiple users which I cannot have. Can we have an option to make it a single choice only. in the attached graphic is the...

When sending work items Azure Boards, bulleted lists don't work properly in Azure. If I have a bulleted list in Aha, tabbing the bulleted list in Azure does not increase the level of the bullets. It just adds tabbed space between the text and the ...

As the service hooks from DevOps to Aha are seldomly failing, it often results in having some records not in sync in Aha. This can be solved by running an update of all the linked records from the Aha integration page, but this requires to be manu...

I'd like to be able to easily see if our engineers remembered to add the PR to each completed feature. Currently it doesn't look like this integration field is available to include in reports.