Azure DevOps Services and Server
Sort by:
Trending
Status:
Future consideration
Showing 108
3
VOTE
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...
2
Future consideration
7
VOTE
Allow linking of Features and Releases to a specific DevOps Iteration Level
We use a more granular structure to the Iterations in DevOps so mapping items to just the top level is not really suitable to keep a feature synchronized correctly and could involve a lot of manual changes at the beginning and end of a release. Fo...
2
Future consideration
5
VOTE
Provide item ranking capability with Azure DevOps integration to Boards
Currently the Azure DevOps Boards integration does not include the capability to share the rank order of items in a workspace which results in the items in the Azure Devops Boards workflow having a different ordering than the items in the Aha rele...
0
Future consideration
1
VOTE
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 ...
0
Future consideration
6
VOTE
Inherit the hierarchy of the area paths from Azure Dev Ops
When integrating with Azure Dev Ops, the area paths should inherit the same hierarchy when represented in Aha. For example, hierarchy in Dev Ops could be: Company/ Company /Functional Area Company/Functional Area/Team The Aha Azure devops integrat...
5
Future consideration
1
VOTE
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...
0
Future consideration
4
VOTE
Allow mapping fields from related records in Aha to Azure Devops
This idea is to allow mapping fields from related records from Aha to DevOps. In most cases, this would be parent/grandparent/great grandparent situations. For example, allowing a tag from an Aha feature to be mapped to a tag on a DevOps PBI. Anot...
0
Future consideration
5
VOTE
Update records selectively
The "Update Records" feature currently updates all integrated records defined in the Azure DevOps integration. This could take quite some time if the number of records is high. Sometimes you only want to upgrade on a particular record type because...
0
Future consideration
2
VOTE
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 ...
0
Future consideration
11
VOTE
Allow VSO integrations to work with multiple Aha Products represented in a single VSO Project
Some customers have specified that they maintain a single VSO Project, but represent a number of products beneath it. The way to handle that now in Aha is to set up a web-hook for each product in Aha, and then create a subscription in VSO that fil...
1
Unlikely to implement