My ideas: Azure DevOps Services and Server
Sort by:
Trending
Filter by:
Status
Showing 91 of 7855
5
VOTE
Sync Release Phase to Azure DevOps
We have adopted a SAFe framework where features are planned quarterly. As a result we are creating 'Releases' in Aha that are materializing these quarters. Within a quarter we may deploy the software multiple times and we are using release phases ...
0
Future consideration
19
VOTE
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
8
VOTE
Integration to Azure DevOps for teams capacity planning
We would like to use Points based capacity planning but it needs to be integrated with (in our case) Azure DevOps which is where the team is committed to and working on work. All of our Features and Master Features (Epics) in Aha are calculated ba...
2
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
1
VOTE
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...
1
Future consideration
1
VOTE
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 ...
0
Future consideration
1
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
16
VOTE
Need full two way integration of a Story with VSTS
Right now you can push a Feature and associated stories to VSTS but if you delete a story in VSTS you have to manually delete in Aha. We need:
1) any story delete in VSTS to be automatically deleted in Aha
2) any story added in VSTS to a Feature...
1
Unlikely to implement
10
VOTE
Ability to set Aha field to a constant value as part of integration field mappings
My scenario is that I have each Aha product linked to multiple different projects in Team Foundation Server (TFS), and I want the features in Aha that come from TFS to have a field indicating what TFS project they came from. But I can’t find a way...
7
Future consideration