Ability to specify and bulk edit 'run as user' in integrations
We have a small team of people who can create integrations. The integration always sets the user who created the integration as the 'run as' user. When we have staff turnover, we have to manually change the integration 'run as' user. There could b...
Steve Dagless
almost 2 years ago
in Integrations
0
Future consideration
As part of system health monitoring we want to be able to monitor integration queues, so that if an issue does occur around data-synchronisation then we can alert an appropriate aha administrator to investigate and fix before the issue becomes wid...
Guest
over 5 years ago
in Integrations
1
Future consideration
Our dev team uses gitlab. When I configured an integration with it, I selected a project where Aha! would push features and new releases (created as milestones in gitlab).
The problem here is that I need to create milestones at the group level ins...
Daniil Novikov
over 5 years ago
in Integrations
2
Future consideration
When configuring a new Product in Aha to integrate with Jira: The backlogs are already in priority order in Jira. However, when syncing over to Aha!, the priority order does not carry over upon the first sync. I understand how to use the rank fiel...
Guest
almost 5 years ago
in Jira
1
Future consideration
Would like to track when a feature was sent to JIRA and by who? Can you please let me know how I can accomplish this?
JIRA_KEY (I am able to pull)
JIRA_KEY_CREATE_DATE (Not known)
JIRA_KEY_CREATED_BY
Thank you
//Need this for SOC compliance//
Sasi Ravichandar
about 5 years ago
in Jira
0
Future consideration
We need the Initiative ID available in JIRA integrations so they can be reference-able in other tool dashboards.
We use the Aha API to populate views in Tableau. The Initiative [API] ID is a crucial portion of making sure what we sync to JIRA from Aha and what we are looking at in Tableau which provides a combined view of both tools, is one and the same. I a...
Wen-Wen Lin
about 5 years ago
in Jira
1
Future consideration
Option to ignore changes to Items that AHA does not know about.
We have joined Azure Dev Ops to Aha via the integrations.
In fact there will by 7+ Integrations due to the size of the portfolio.
We have restricted the webhooks so that:
New / Updates to (Release / Epic Work Item types) are pushed to AHA from ...
Guest
about 5 years ago
in Integrations
0
Future consideration
Add strategic models as an activity in the Teams integration
Who would benefit? Those who need to know when something in the model changes What impact would it make? This would allow us to keep all people working on a product up to date with the latest information. How should it work?
Debra Hunter
about 1 year ago
in Integrations
0
Future consideration
We are storing a client name on user stories and bugs in ADO and it would be great to be able to be able to sync this field between ADO and Aha! using the organization field that has now been made available to all Aha! objects (and not only ideas)...
Nicolas Andrillon
about 3 years ago
in Integrations
0
Future consideration
Ability to apply a Jira Integration Template to an EXISTING Jira Integration but only have it update the URL and Jira Login/Password settings
We had a very large number of Jira Integrations created before we had central administration of our Aha application. I need to apply a Jira template to these integrations so that the URL and password can be managed from a central person, but if I ...
Leanne Miller
about 4 years ago
in Jira
0
Future consideration