Azure DevOps Services and Server
Sort by:
Trending
Status:
Future consideration
Showing 99
1
VOTE
Add Markdown support for ADO integration
What is the challenge?
Markdown editing has been added in Azure DevOps for rich text fields. However, when the data is migrated to Aha, it's stored as raw Markdown rather than displaying as formatted text.
What is the impact?
Makes integra...
0
Future consideration
33
VOTE
Allow attachments to Feature comments to be integrated to Azure DevOps
When you add comments to a Feature, and you have integration with Azure DevOps (ADO) configured, you can have these comments passed back and forth. Unfortunately if you attach a file to a comment it will not get passed between Aha and ADO. When yo...
0
Future consideration
5
VOTE
5
VOTE
Bi-directional support for Area Level fields in ADO integration
What is the challenge? Currently we offer Area Level fields in our ADO integration for each Area Level. This allows us to receive the unique Area Level from ADO, but currently updates in Aha! do not change the Area Level back in ADO despite the se...
0
Future consideration
1
VOTE
Enable Roll-up Initiative link in the standard Azure DevOps Services integration
What is the challenge?
Unable to integrate multi-layered strategic initiatives from Aha to ADO
What is the impact?
Manual updates to keep information in sync, prone to errors. Question whether we will continue to utilize Aha or work direct...
0
Future consideration
3
VOTE
Add ability to map Created by Field between Aha! and ADO Server accounts
What is the challenge? Currently there are a few user fields from ADO server accounts available to map to Aha!'s Created by User, but the Created By user is not displaying as an option. What is the impact? Users are unable to map the created by fi...
0
Future consideration
3
VOTE
Allow use of Mapped fields template with one field difference for each integration
What is the challenge? Can't use Mapping Integration template. Have to update multiple integration for every mapping change since one has to be different. What is the impact? Would save a ton of time for our team. Describe your idea We have around...
0
Future consideration
29
VOTE
Keep features in sync when they cross areas in Azure DevOps
This is useful when you have your DevOps areas configured by team. Once the features are pushed from Aha! to DevOps and evaluated by the team they need to be moved into the area for the appropriate team. Any team can work on any feature based on a...
0
Future consideration
27
VOTE
Allow a single Azure DevOps webhook to support updates across multiple Aha! integrations
With Jira, a single Aha! webhook added at the system level supports updates across all Aha! integrations.
This makes scaling integrations simple as after the first setup, a user never has to add another webhook.
With Azure DevOps (TFS), each i...
1
Future consideration
28
VOTE
© 2024 Aha! Labs Inc.•All rights reserved