ADD A NEW IDEA

Integrations

Showing 916 of 8640

Allow parent mapping of releases to initiatives

In ADO we use assign our epics as children of themes. In AHA we map themes to initiatives and epics to releases but in the integration configuration we cannot set the parent mapping.
Joe Granville over 4 years ago in Azure DevOps Services and Server 0 Future consideration

Map to a persona name value in integrations

Right now we leverage personas to describe who a release is targeting, where we'd love to be able to push the text value into our JIRA mapping
Barnett Klane over 4 years ago in Jira 3 Future consideration

Integrate with Miro

Hi, would you consider integration with Miro, formerly RealTime Board? This is a great diagraming app, and has a good Jira integration which I was going to use in a convoluted way by pushing from Jira to Aha to get visibility back in Aha. In reali...
Guest over 4 years ago in User story map / Wanted 10 Future consideration

DevOps Integration issue with multiple attachments default name Image.png

See the support request# #408720 for the integration error with for a work item with more than one attachment with same name. Resolution provided by Aha! support is to rename the image.png files differently so that DevOps accepts them. Can Aha! Im...
Sekhar Nallapaneni over 4 years ago in Azure DevOps Services and Server 0 Future consideration

Integration with BOM Software

Has there been any thoughts or conversations with BOM software apps to integrate with Aha!? Tracking BOM for hardware products is very complementary to Aha!. So, rather than, say, attaching spreadsheet files (containing a BOM) to any single Featu...
Guest over 4 years ago in Integrations 0 Future consideration

Progress Bar calculation based on integration

Today, in order to use the progress bar, we must pull requirements/user stories into Aha. For me, user stories are more granular and owned by our engineering team in CA Agile (Rally). There is already a field in Rally called percent done by story ...
Ali Stuck over 4 years ago in Integrations 1 Future consideration

Ability to aggreate work done value from both feature and requirements

Dear aha, in our scenario when AHA is synced with JIRA with time tracking attributes, we come into a problem with showing the complete work done on the feature when: 1. there is a time log in JIRA on epic (synced to feature) 2. there is a time l...
Daniel Pokrývka over 4 years ago in Jira 2 Future consideration

Update the JIRA sprint field with better import

Currently if a story has belonged to more than one sprint, the sprint field concatenates the sprint. For example, a story was in sprint 2019.5 and then moved to 2019.16 and then moved to unscheduled. In JIRA the story is none +2 indicating tha...
Guest over 4 years ago in Jira 3 Already exists

Expose scorecard metrics as integration fields

Currently, scorecard metrics do not appear to be available to integrations. We would like to represent these components in our development system in the interest of transparency to our development teams, but there is no way to get this data across...
Bob K over 4 years ago in Integrations 3 Future consideration

Allow a single Azure DevOps webhook to support updates across multiple Aha! integrations

With Jira, a single Aha! webhook added at the system level supports updates across all Aha! integrations. This makes scaling integrations simple as after the first setup, a user never has to add another webhook. With Azure DevOps (TFS), ea...
Guest over 4 years ago in Azure DevOps Services and Server 1 Future consideration