When we disable an integration to Jira, we mean it to be we have a new Jira project to integrate to. It makes it easier on the integration on the feature to not have a huge list of Jira projects to integrate to and only to the projects that are ac...
Carina Velazquez
about 1 year ago
in Integrations
2
Future consideration
Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.
Wayland Fox
over 3 years ago
in Jira
0
Future consideration
I'd like an option to create a webhook that will send me messages when integration errors occur. I will use this webhook to create messages in Teams, so I know that I should go to either Aha or the source system to fix the issue.
David I.
3 months ago
in Integrations
0
Future consideration
Map VSTS/TFS picklist custom fields to Aha! choice list fields
VSTS/TFS picklist custom fields are treated as strings and cannot support option mappings. Mapping a picklist field to an Aha! choice list field should provide the option to click Configure and map the choices.
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...
If comment is deleted in Jira, add a tag <Deleted> to Aha to ensure users are aware of the change (& Vice versa)
What is the challenge? currently, comments that are deleted on one platform, do not get deleted on the other platform (& Vice Versa) What is the impact? Users who work dedicatedly on Aha (like Top Management) will continue to view out-dated co...
Maria V
3 months ago
in Features / Jira
0
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
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
over 1 year ago
in Jira
0
Future consideration
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