Skip to Main Content
ADD A NEW IDEA

FILTER BY CATEGORY

Azure DevOps Services and Server

Showing 94 of 8300

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 about 2 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 2 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 5 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 7 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 8 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 9 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 9 months ago in Azure DevOps Services and Server 0 Future consideration

Update the Feature % Complete field based on User Stories of the DevOps Feature

Update the Feature % Complete field based on User Stories of the DevOps Feature that is linked to the Aha Feature. The Software Product Plan does just that! In DevOps, this information is a calculated field, which can be easily configured in Board...
Guest 11 months ago in Azure DevOps Services and Server 1 Planning to implement

Aha! Releases Should Honor ADO Area by Default

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 ...
I R 11 months ago in Azure DevOps Services and Server 0 Future consideration

Function as a hub to push data from JIRA to DevOps

We use JIRA internally for tracking most of our development work, while a customer we work for uses DevOps. We also use Aha. We would like our customers to be able to see JIRA comments pushed through to DevOps. We tried to use Aha as a 'hub' to do...
Guest 11 months ago in Azure DevOps Services and Server 2 Future consideration