Skip to Main Content
ADD A NEW IDEA

Azure DevOps Services and Server

Showing 96

Sync the change of parent link made in Aha! across 2 Azure DevOps integrations

Who would benefit? Customers with multiple integrations set up to ADO who are wanting to move features to different Epics as their plans change. What impact would it make? How should it work? The parent/child relationship should be tracked across ...
Stuart Blair 19 days ago in Azure DevOps Services and Server 0 Future consideration

Exportable list of orphaned workitems in Integrations update modal

Who would benefit? Aha admins, dev lead What impact would it make? Improved collaboration, minimizing integrations admin How should it work? Use case: I want to inform and support development team creating Azure Devops work items on Requirement le...
Mats Hultgren about 1 month ago in Azure DevOps Services and Server 0 Future consideration

Support AzureDevOps "work item deleted" events so my Aha records aren't out of date

Who would benefit? Anyone who manages an Aha board that syncs with Azure DevOps (ADO) What impact would it make? It would reduce out-of-date information in Aha & on roadmaps from records that rely on the ADO integration for updates. Additional...
David I. about 1 month ago in Azure DevOps Services and Server 0 Future consideration

Warn user of integration on epic deletion

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...
Tom Bailey 5 months ago in Azure DevOps Services and Server 0 Future consideration

Show name of user whose token is being used in ADO integration

Who would benefit? Admins of accounts with ADO integrations What impact would it make? When an ADO integration is created, a user with the correct permissions must enter their token to authenticate the integration. However, the token owner's name ...
Bonnie Trei 6 months ago in Azure DevOps Services and Server 0 Future consideration

Add warning text to Custom field Key field description that changing the key value will break integration

We found that changing the key-field string of a custom field will break existing integrations with ADO where the custom field is synced to an ADO field. There is no warning or anything. This is a big risk to us and to the trust that integration r...
Rob Boutmy 9 months ago in Azure DevOps Services and Server 0 Future consideration

Ability to refresh data from the development tool for a single Aha record

Sometimes I'd just like to fix a record or two that have gotten out of sync. When I click on the Integrations menu for a particular feature, I have the option to resend all fields to my development tool (Aha -> ADO), or, to delete the link. IDE...
Kim Bremer 10 months ago in Azure DevOps Services and Server 0 Future consideration

Better presentation of text when integrating to an existing field in ADO

Sometimes, the feature in ADO already exists, and I want to link it to a feature in Aha. When I do this, I'm presented with an un-readable HTML output of the description fields, making is pretty much impossible to actually see the differences. See...
Jake Hawkes 12 months ago in Azure DevOps Services and Server 0 Future consideration

Include author of comment from Azure DevOps when saving to Aha

We use the Aha <-> Azure DevOps integration. Comments from Aha include the author when synced to AzDO (Comment added by <user> in Aha! - View). The reverse is not true. Comments made in AzDO that come to Aha do not say the other, just ...
Guest 12 months ago in Azure DevOps Services and Server 0 Future consideration

Allow link of a requirement to a release (sprint)

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...
Guest about 1 year ago in Azure DevOps Services and Server 0 Future consideration