ADD A NEW IDEA

FILTER BY CATEGORY

Jira

Showing 61 of 6672

Force Status field to be in sync with Jira

The recommendation of keeping Status as a one way sync from Jira makes Aha! reports silently unreliable, as Aha! and Jira status will diverge if somebody touches a record "by mistake". If I set it to two-way sync, transitions not allowed by Jira ...
Daniel Hirschberg 11 months ago in Jira 1 Shipped

Use the JIRA URL field to show the JIRA link

I have JIRA linked with Aha! and can see the JIRA Id and key - which is great. But I would love to have the URL link available in my list report as well. It looks like there is a field JIRA URL, but it is blank. What is it used for?
K Wollery about 1 year ago in Jira 4 Shipped

Support the "links to" field mapping with 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" ...
Jordan Skole about 2 years ago in Jira 12 Shipped

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...
Robyn Diamond about 2 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 over 2 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 over 2 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 over 2 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 i...
Michael Weldert over 2 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 2 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...
Justin Woods almost 3 years ago in Jira 7 Shipped