This would allow the project management team to review and manage the project in AHA! and collaborate with Global teams on MS TEAMS by integrating the tasks.
Shane SWINEHART
about 5 years ago
in Integrations / To-dos
0
Future consideration
JIRA integration to track correct users in history of issues
Today the Aha JIRA integration will leverage the user account setup in the integration settings as the actor for all integration sends between the systems. This creates a lot of confusion for who actually made changes in one system or the other. F...
Austin Churchill
about 4 years ago
in Jira
1
Future consideration
be notified in Aha! when an item is deleted in Rally
We are creating connection between Aha! and Rally records.
It may happen that record are moved in different Rally project or may be deleted. But there is no way to have such information in the Aha! record.
Today the integration between the 2 items...
Guest
about 6 years ago
in Rally
2
Future consideration
Jira integrations : Add the capability to use filters instead of boards to set up integrations
What is the challenge? the boards only have tickets currently worked on , we want to load all tickets , so we can plan , this is because the team sometimes their create their own What is the impact? if you need to split a jira project with multipl...
Guest
about 1 year ago
in Jira
0
Future consideration
Currently the Google Drive integration only supports access to the My Drive folder. It would be extremely helpful if the integration supported access to any Shared folders in the Google Drive as well so that users don't have to copy files from the...
Guest
about 8 years ago
in Integrations
5
Already exists
Sync sprints between requirements in Aha! and equivalent (e.g. PBIs) in Azure DevOps
Our development team manages PBIs within sprints. Currently you can map a custom sprint field for features in Aha! to DevOps, but not requirements. Ideally, we would be able to sync sprints for requirements/PBIs, as that would be more useful than ...
Within the JIRA integration, add the ability to hide options to 'send to' JIRA and only show the 'link with existing' options. This would be helpful for integrations that are designed/configured to be only 1 way (JIRA to Aha).
Kyle Kinder
about 2 years ago
in Jira
1
Future consideration
Calculated mapping of number fields in integration with Jira
We would like to specify a conversion factor or formula to map numeric fields between Jira and Aha! numeric fields, especially a Jira number field and Aha!'s Original Estimate field. This would allow us to enter hours into a Jira number field whic...
Jor Bratko
about 3 years ago
in Jira
0
Future consideration
Nested Iteration Paths with VSO / Visual studio team services integration
We have the same VSO project for many products in Aha. We would like the ability to have child iterations for releases so we can group them together in our queries. Current integration only allows us to go 1 level deep in the iteration path.
Our...
As an Aha user, when I create a Requirement with a Comment which is mapped to Azure DevOps I need the initial Comment to synch to Azure and not just subsequent Comments Working with offshore teams, and not able to speak to them during off hours, w...