-
Integrate Aha! and Confluence to link Confluence Pages in AHA! and transfer them with JIRA
Atlassian currently offers the ability to Integrate Confluence & Jira using Application Links which gives teams multiple features. https://confluence.atlassian.com/doc/use-jira-applications-and-confluence-together-427623543.html One of the fea...5 Future consideration
-
Update records on all integrations linked to a template at one time
We anticipate having 150+ integrations based on a template (with the Rally integration). In order to add fields to the integrations, we edit the template and those updates/new fields flow to the individual integrations based on the template, howe...0 Future consideration
-
Add 2-way integration mapping for release start and end dates
Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release.Now that this date is set manually, it should be possi...
0
Future consideration
-
Product Integration Details from API
See https://support.aha.io/hc/en-us/requests/465310 for reference. We're performing additional analytics outside of Aha that combines Aha and JIRA data. In order to effectively do this, we need to be able to tie an Aha Product to a JIRA Projec...0 Future consideration
-
Trigger slack notifications based on updates to custom fields in aha
We use a custom 'Status update' field to track and communicate the details around current status of an initiative. This field is updated by the product management team weekly and/or whenever there are key updates (that may not require an actual "s...0 Future consideration
-
Support "Agility" (next-gen) Templates in Jira
My team really likes the simplicity of the "Agility" templates in Jira, sometimes called "next-gen" templates. Through the Jira integrations, we are able to sync almost everything that we need, except for the relationships using the "Linked to" ...11 Future consideration
-
Don't show 'Engagements' section in all workspaces when a Google Analytics integration is set up
Currently if a google analytics integration is configured, all workspaces in the entire account get an 'Engagements' section added to their records (ex: feature card). This causes a lot of visual clutter for the workspaces which are not using this...
0
Future consideration
-
JIRA Integration: Adding Master Feature, Initiative & Goal Record Links
The use case is so that those working primarily in JIRA can understand “why” they are being asked to deliver “what” has been requested. In the screenshot attached, it shows a section of the JIRA issue interface. It then shows a tab created specifi...1 Future consideration
-
Ability to map an initiatives "assigned to" field with a user field within an integration
When mapping an initiative to a record in a development tool, it would be helpful to have the ability to map the "assigned to" field from Aha! to a user field. This would be helpful when initiatives are mapped to EPICs so the assigned user can sy...
0
Future consideration
-
Allow Aha! user name to populate DevOps board user
When working with multiple users, we need to be able who created what, commented on or changed something. As of right now, the user name (Admin) of who configured the Integration (Azure DevOps Services) is the one that appears on every item in D...2 Future consideration