Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 919 of 8698

Integrations 2.0: Allow Master Feature relationship for Requirements

I can create a relationship for Releases at the requirement level even though requirements do not inherently have a release field, this appears to be derived from the feature. I should also be able to create a relationship to the Master Feature in...
Danny Archer over 6 years ago in Integrations 0 Future consideration

Set Dates of Feature Based on Status in JIRA

I'd like to see the Aha!/JIRA integration be updated to have an option to set dates of features (and possibly other items) based on Status that is in JIRA. Example: I create a Feature in Aha! and integrate/export to JIRA When Feature (referred t...
Aaron Kremin over 6 years ago in Jira 0 Unlikely to implement

Salesforce Integration - Need hierarchical dropdown section from within the AHA UI to make it more feasible to select the correct product for which an idea is requested.

The issue with the Salesforce integration is that you can only map to one ideal portal. That would require us to only have a single idea portal for all products across all Divisions. So when the Sales rep tries to submit an idea or browse existing...
Christian Stark over 6 years ago in Integrations 0 Future consideration

Integrations 2.0 - Only show valid integration directions for Release <-> Fix Version

Integrations 2.0 - Please only show valid integration directions for Release <-> Fix Version. I had opened ticket https://support.aha.io/hc/requests/176083 because I could not connect to the Jira version using Actions > "Link with existin...
Guest over 6 years ago in Jira 0 Unlikely to implement

Integrations 2.0: Add dependency link to connect records without natural relationships together

In integrations 1.0 if I mappedFeatures = StoryRequirement = TaskAha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other.In 2...
Danny Archer over 6 years ago in Jira 3 Future consideration

Jira 2.0: modify integrations based on templates

In 1.0, when using a template, you could choose what fields/behaviors to inherit from the template, and which to customize for that particular integration. This was useful for custom fields (now using a constant in 2.0) which will change from prod...
Max Cascone over 6 years ago in Jira 6 Already exists

Synchronise mockups to other integrations

Currently, when a mockup is updated or deleted, the file does not stay in sync with an integrated system. Ideally, the same mockup file would continue to get updated across the systems.
Toray Altas over 6 years ago in Application / Integrations / Mockups 1 Future consideration

Properly send mockups to Github

Mockups are being sent to github as links, opening the image externally, instead of showing them directly in the issue. Prepending the link with an exclamation mark would show the mockup inside the github issue, a much useful approach. Current mo...
Guest over 6 years ago in GitHub 4 Already exists

Integrate Sharepoint calendars with Aha! calendars

So, for planning purposes, we still have a release schedule. Not really an agile shop, so we still have release dates and blackout windows. As product manager, we are looking out 12-18 months across our roadmap and performing customer adoption imp...
Guest over 6 years ago in Integrations 0 Unlikely to implement

Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field

Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field - prevents having to go to JIRA and add points individual after time spent planning in AHA! - efficiency for PMs and Engineering
Guest over 6 years ago in Jira 1 Future consideration