Skip to Main Content
ADD A NEW IDEA

My ideas: Integrations

Showing 273

Create AHA reference automatically after import rather than having to 'resend' all data fields back to the place I have imported from.

After I have imported a record from Jira I then have to ‘resend all the fields’ from AHA in order for the AHA reference to be populated. Is there anyway that on import an AHA reference is created at that point?
Guest over 6 years ago in Jira 0 Shipped

Allow TFS integration to populate 'Replication steps' for bugs created in Aha

To be able to easily create bugs from within Aha and use the TFS integration to pull across all relevant info from the description field into reproduction steps. After a long investigation by Aha they found that this link was not created as part o...
Andrew Barber over 6 years ago in Azure DevOps Services and Server 0 Shipped

Allow more than one Salesforce instance to connect to AHA

Usually before you roll out big changes to any Salesforce instance you test this in a Sandbox. We would however like the Salesforce Sandbox connection with AHA to continue to function to further test profile changes and their impact on the AHA con...
Christian Stark over 6 years ago in Integrations 1 Shipped

Integrations 2.0: Selectable behaviour for importing new records when multiple Aha! products integrate with a single JIRA project.

Often teams will integrate multiple Aha! products with a single JIRA project. Currently the import behaviour in 2.0 is you get 'n' number of import candidates which appear in the "Import New Records" modal for all integrated Aha! products regardle...
Guest over 6 years ago in Jira 7 Shipped

Sync "Sprint" Field from JIRA

Would like to be able to view the sprint a feature is currently assigned to in JIRA. It looks like we have most of the other fields available for mapping but that one isn't available. I get a ton of questions about when a feature is scheduled to b...
Guest over 6 years ago in Jira 2 Shipped

Bulk Edit Mappings

One of the fields we have in JIRA has over 100 values. Mapping each value to Aha is a no go. The interface to manually drag and drop each value to the correctly mapped value is slow, cumbersome and took over 60 seconds to just do 1. It will be pr...
Project Parker over 6 years ago in Jira 3 Shipped

Custom Scorecard support for Features and Requirements

We use a custom scorecard to add priorities to our Requirements (user stories). With our JIRA integration, I NEED to be able to map this priority score to a custom field in JIRA.
Guest over 6 years ago in Integrations 3 Shipped

Integrations 2.0: Support importing unmapped issue types

In 1.0 you could map Features to Stories but also set the JIRA integration to support importing unmapped types. This meant that bugs, tasks, etc created in JIRA could be imported as Features in Aha! This is important, without this we have no way t...
Danny Archer over 6 years ago in Integrations / Jira 8 Shipped

Integrations 2.0: Support JIRA Priority field mapping

In 1.0 I could map a custom field to the priority field in JIRA. In 2.0 it appears as an option but the Aha! fields it can map to are only the name/description. It doesn't allow mapping my custom field to the JIRA field.
Danny Archer over 6 years ago in Integrations 0 Shipped

Integrations 2.0: Support "Link to existing" functionality from 1.0

In 1.0 you had the option with JIRA to link to existing records. This would let you connect an existing record in Aha! with an existing record in JIRA. This support should exist for 2.0 integrations.
Danny Archer over 6 years ago in Integrations 8 Shipped