Skip to Main Content
ADD A NEW IDEA

My ideas: Azure DevOps Services and Server

Showing 103 of 8706

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 almost 6 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 about 6 years ago in Azure DevOps Services and Server 0 Already exists

Allow DevOps URL in Integration to be different for connected workitem links

Our DevOps AHA integration is using a dedicated subdomain that only allows the AHA Server IP in for obvious security reasons. Now when users click integration links within AHA's User Stories the link will not resolve as their IP gets blocked. It w...
Michael Scholze over 3 years ago in Azure DevOps Services and Server 0 Future consideration

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 over 7 years ago in Azure DevOps Services and Server 1 Unlikely to implement

Ability to execute a AzureDevOps query and display results in charts on Aha Dashboard

For the teams who uses AzureDevOps as ALM tool , It would be great flexibility to view a snapshot of the query results on the Aha dashboard. It does not need to be sync but can be pulled async.
Guest about 4 years ago in Azure DevOps Services and Server 0 Future consideration

Allow TFS integration to map bidirectionally for fields that are not in a built-in System.State.

Currently, the TFS integration does not support mapping arbitrary string fields to the Aha! workflow status field in a bi-directional way. Only the built-in System.State field in TFS can be mapped bidirectionally.
Guest about 4 years ago in Azure DevOps Services and Server 2 Future consideration

DevOps Integration issue with multiple attachments default name Image.png

See the support request# #408720 for the integration error with for a work item with more than one attachment with same name. Resolution provided by Aha! support is to rename the image.png files differently so that DevOps accepts them. Can Aha! Im...
Sekhar Nallapaneni over 4 years ago in Azure DevOps Services and Server 0 Future consideration

Automatically create webhooks by default for Azure/TFS

No description provided
Guest about 5 years ago in Azure DevOps Services and Server 0 Future consideration

Converting requirements to features after integration

Converting a requirement to a feature will cause the record to lose some custom field information because features may not have the same custom fields. We can choose whether or not to proceed. There's no mention of integration to an external syste...
Tom Beck over 5 years ago in Azure DevOps Services and Server 1 Future consideration

VSTS Integration - Error importing new records into Aha

As we are starting to use more and more Aha!, we are seeing errors while newly created records by Development team in VSTS being imported into Aha!. 2 main reasons for the errors include Feature is not available for the user stories (Requiremen...
Sekhar Nallapaneni over 5 years ago in Azure DevOps Services and Server 1 Already exists