Integrations
Sort by:
Trending
Status:
Showing 947
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
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
1
VOTE
Defect: Jira Integration record mapping doesn't use custom terminology
Who would benefit? Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration. What impact would it make? Prevent failure of the integration (which took us several hours to figure out). This was particularly egregious fo...
0
Future consideration
1
VOTE
Allow project access token to be used instead of personal token for GitLab integration
Who would benefit? anyone using the integration with aha and GitLab What impact would it make? improves resiliency and stability of the integration How should it work? Currently, to set up the GitLab integration a user in GitLab must use a persona...
0
Future consideration
11
VOTE
Support an integration with BetterWorks to sync goals, success metrics and initiatives
As a company adopting a next generation performance management system anchored in the concept of Objectives and Key Results I would like to synchronize Aha goals, success metrics and initiatives with BetterWorks (www.betterworks.com)
Note: both Be...
0
Unlikely to implement
1
VOTE
Iteration to Release not Retaining Parent Relationship with other Records (AzDo Integration)
Who would benefit? Aha users What impact would it make? Elimination of lost records (Azdo integration) How should it work? When using iteration to release, the integration would look at the area path of that record as well as the iteration path. S...
0
Future consideration
5
VOTE
8
VOTE
Persistent filters for integrations and incoming product updates
Using JIRA integrations, I have an Aha product that spans several JIRA projects. To work with this I have set up an integration per project with a specified JQL filter. For example my filter could include "priority = high". Other products througho...
0
Future consideration
1
VOTE
Add Actionable Agile into your dev product
Who would benefit? anyone using Kanban and want's accurate process measurements What impact would it make? Better insights into the flow of work in your system, better forecasting of future work without having to ever ask for estimates that are mo...
0
Will not implement
12
VOTE
Set the TFS Iteration and Area path per feature or requirement
Having a single area path for the entire product doesn't make sense. This value will usually depend on the feature, as area paths define the area of code impacted by a work item. This helps with evaluating code churn and test coverage. It needs to...
6
Already exists
© 2024 Aha! Labs Inc.•All rights reserved