Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 948

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"...
Guest 5 months ago in Azure DevOps Services and Server 0 Future consideration

Ability to import child records when connecting to an existing record in Jira

What is the challenge? We often have the use case where we need to connect an Aha! epic to an existing Jira record, and that Jira record will also likely have child tasks/stories. The existing connection logic will only sync with the epic record, ...
Nerissa Muijs 5 months ago in Jira 0 Future consideration

Allow mapping to the Rally iteration field

There is a built-in Rally field named iteration. It would be useful in many situations to map the iteration field to an Aha! field.
Austin Merritt over 2 years ago in Rally 3 Future consideration

Allow for parent-child linking across Jira projects without using an integration template

Some organizations that use SAFe store high-level records in one Jira project and the tactical work in team-specific Jira projects. These are often integrated to the same Aha! workspace. Today, you have to use the same integration template in the ...
Emily Yankush about 1 year ago in Jira 0 Future consideration

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...
Deb Gay over 5 years ago in Azure DevOps Services and Server 0 Future consideration

Support new tasklist structure in Github

Github is adding functionality to extend how tasklists are used and increase tracking and linkages between items. The Aha integration should be capable of supporting this - particularly the linkages and tracking between related items https://docs....
Guest over 1 year ago in GitHub 2 Future consideration

View in Aha! the author of a comment created in Azure DevOps

In integrations with Azure DevOps, comments created in ADO show the integration name rather than the individual as the creator of the comment when looking at it in Aha!. This can cause confusion for Aha! users who can't easily understand the conte...
Guest over 3 years ago in Integrations 1 Future consideration

Please add worksheet field in mapping of aha! JIRA integration configuration.

Who would benefit? What impact would it make? We can integrate worksheet field with JIRA. How should it work?
Guest 8 months ago in Integrations 0 Future consideration

Jira integration user name

In both Jira and Aha!, you need to have a user that has the appropriate permissions which is often a highly privileged user. However, when setting up the integration, there is no way to indicate an alias name to use for the integration. Consequent...
Karie Kelly over 2 years ago in Integrations 0 Future consideration

Improve formatting of Slack messages

Who would benefit? Internal Users What impact would it make? Improved Team Visibility and Communication How should it work? Concise format instead of tabular messages, ability to create filters
Guest 8 months ago in Slack 0 Planning to implement