Skip to Main Content
ADD A NEW IDEA

Jira

Showing 85

Ability to sync more than one Issue Type to a Record

It's critical for us to track bugs/defects in Aha! related to a specific release but these bugs/defects belong to Features that have other WIP Stories. We need to be able to sync different Issue Types from JIRA to the Requirement record in Aha! Th...
Guest almost 6 years ago in Jira 1 Shipped

When a feature is linked to an existing epic in Jira, sync the child stories to Aha! as requirements

We map Aha! features to epics in Jira, with Aha! requirements as stories. When an epic already exist in Jira with child stories, I want to link that epic to a feature in Aha! and have the child stories immediately sync over as requirements.
Kelly Sebes almost 6 years ago in Jira 0 Shipped

Allow a Feature (epic) in Aha! to have Requirements (stories) that live in a different Jira project

The use case is that we create features in Aha! and sync them to Jira as epics. The development team will then break the epics down further into stories in the appropriate Jira projects for the teams that need to work on them. In Jira, these stori...
Kelly Sebes almost 6 years ago in Jira 3 Shipped

Auto-field mapping for Jira Integration

I have created a custom field in Aha which maps directly a field in Jira. I have created a pre-defined choice list in Aha! which contains all possible values in Aha!. When creating the integration between Jira and Aha! I have to manually match eac...
Matt Gunnell about 6 years ago in Jira 0 Shipped

Enhance JIRA Integration Controls

The current JIRA integration Updates feature has limited control capabilities. You can select or ignore items to bring into Aha! The problem is that if you "ignore" a card, it doesn't stick, so any update to the card in Jira mandates that you igno...
Michael Weldert about 6 years ago in Jira 0 Shipped

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

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

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