My ideas: Azure DevOps Services and Server
Sort by:
Popular
Status:
Future consideration
Showing 108
3
VOTE
3
VOTE
Automate service account password updates for TFS integrations
Right now we have a TFS integration configured with Aha which requires us to use an AD service account for TFS. This service account password needs to be manually added within Aha! however we have a policy that all our service accounts require pas...
0
Unlikely to implement
2
VOTE
Expand the Jira migration tool to support migrating Azure from Server to Services
What is the challenge? There is a tool to aid users in migrating from Jira server to Cloud, but it does not currently support ADO migrations. What is the impact? Users who need to migrate ADO have a manual process to relink records after moving to...
0
2
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
2
VOTE
Enable tags to be a selection for Azure DevOps integration of requirements
What is the challenge? You can sync tags for features but not requirements, What is the impact? creates duplication of work having to recreate tags in Azure DevOps Describe your idea As part of the field mapping for Azure DevOps integration "tags"...
0
Future consideration
2
VOTE
Warn user of integration on epic deletion
Who would benefit? Integration users What impact would it make? How should it work? When you delete a feature which is linked to a dev system you get a warning (attached). When you delete an epic, you do not get a consitent warning. This suggestio...
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
2
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
2
VOTE
Links to Azure DevOps items should be dynamically created based on integration settings
We underwent a branding change and had to update our Azure subdomain and after updating all our workspace integrations in Aha!, the hyperlinks (Azure DevOps Services url) were still pointing to the old subdomain and there is no way to refresh them...
0
Future consideration
2
VOTE
Limit workspace users choice to 1 user instead of multiple (like the Assigned to) field
I need to add the workspace users as a custom field in my template and currently it doesn't limit to just one user, it allows multiple users which I cannot have. Can we have an option to make it a single choice only. in the attached graphic is the...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved