ADD A NEW IDEA

FILTER BY CATEGORY

Azure DevOps Services and Server

Showing 93

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 almost 5 years ago in Azure DevOps Services and Server 0 Future consideration

Sending Sprint to VSTS with complex organization

I can't get my Sprint to land in the right area, it winds up under main as another project instead of sprint under a project when structure is Main>Project>Sprint.
Guest about 5 years ago in Azure DevOps Services and Server 0 Future consideration

Don't fail TFS Integration when attached file is too large

When a file has been uploaded to aha that is larger than the maximum file size,then integrate without the file in TFS, adding a note indicating this. This will allow the team to collborate on the TFS items without having to delete the file.
Guest about 5 years ago in Azure DevOps Services and Server 0 Future consideration

VSTS updating Aha! features base user stories

Leadership and executives are using Aha! more and more. Having the ability to represent the percentage completed of features in a given release is very important when reporting to large audience. I like to ability to show the percentage of the Fe...
Guest over 5 years ago in Azure DevOps Services and Server 0 Already exists

Would it be possible to not need a paid AHA account to process VSTS updates?

At the moment we have set up the VSTS integration with a paid AHA account as required. This means that all updates come in from that product manager. In the history threads, and the notification emails we get a combination of VSTS updates, and the...
Guest almost 7 years ago in Azure DevOps Services and Server 1 Unlikely to implement

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 3 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 4 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 6 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 6 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 7 months ago in Azure DevOps Services and Server 0 Future consideration