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
9 months ago
in Jira
0
Future consideration
We would like to be able to copy and move an integration template from one workspace to another. This would allow us to restrict access on the template if we could move it to a location that no regular users have access to. We can then use that te...
Elaine Edwards
over 4 years ago
in Integrations
4
Future consideration
I really like the VSTS integration 2.0, however could you add Area Path to the list of available fields that can be mapped to. This would be useful as in VSTS we use Area Path to note which dev team has picked up a feature and it would be great to...
Filter capabilities on the Integration Update Import screen
As one Product Owner of a very large product that has a lot of product owners, I would like more filter capabilities on the Integration Updates import screen so that I can only see items that pertain to my portion of the backlog. This request is s...
The log file currently reports on Jira tickets that are out of scope for the integration (e.g., bugs, stories, tasks) as defined by the integration template. These log entries typically end with "No changes made in Aha!" If I'm trying to find the ...
Sandy Kobayashi
almost 2 years ago
in Jira
0
Future consideration
I have set up Aha to integrate with Jira (development team) and Looper (field team), I would like to be able to have a seemless "automated" way to link comments and status between ideas and features. The idea being when Jira development teams have...
Chad Tidd
over 4 years ago
in Integrations
0
Future consideration
When, for example, an idea is created within aha! and the integration alerts a slack channel of this entry, it would be good to be able to customise the output of that notification and remove unwanted fields.
Guest
almost 4 years ago
in Slack
2
Future consideration
Who would benefit? Users of both Aha and those who are not direct users of Aha on a daily basis but who relay on outputs from the platform. What impact would it have? It would simply data sharing and through Microsoft products such as Teams, Word,...
Guest
about 1 year ago
in Integrations
0
Future consideration
Ability to filter records in the ‘integration updates’ based on a field (eg: categories or tags)
Currently Integration update brings in all new records from Rally project. And there is no way to filter the data before import. Want the ability to filter on some Rally fields (eg. status & tags) which will help to import on the required reco...
Jyothirmayi Talaparthy
over 4 years ago
in Rally
2
Future consideration
Allow additional Link Types in the 'Links to' field
Within AHA we are mapping
Releases -> ADO Release Work Item
Master Feature -> ADO Epics
Features -> ADO Features.
Master Features need to be located in the Release in which they complete. But Features (that contribute to this Master F...