Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 276

Push mock-ups from Aha! to Jira Draw.io plugin

We create UX/UI mock-ups in Aha!, and I would likedevelopers to be able to see them after the feature is pushed into their Jira backlog. I noticed that both Aha! and Jira use Draw.io for mockups. Is there any way Aha! can upload mock-ups associate...
Guest almost 7 years ago in Jira 4 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 about 8 years ago in Jira 0 Unlikely to implement

Allow "Predefined choice list" to select multiple items

Jira has the ability to have a custom field with selecting multiple items in a list. Aha can only support single items. The Aha multiple tags functionality is incompatible with Jira selects. We would like the ability to specify 2 or more items in ...
Guest over 9 years ago in Jira 0 Unlikely to implement

Add support for JIRA panel formatting

Currently JIRA panel formatting is not supported. This results in Aha! turning panels into bullet point lists.
Danny Archer almost 10 years ago in Jira 0 Will not implement

JIRA integration without admin account rights

At the moment, for the JIRA integration the JIRA account used to connect must have admin rights. This doesn't work for our security protocols because that would mean we're opening up access to secure projects that live in the same JIRA instance th...
Guest almost 11 years ago in Jira 0 Already exists

Ability to map editable choice lists in Aha! with the Jira Team field and support bi-directional sync

What is the challenge? Bi-directional sync of the Jira team field is only supported for some Aha! custom fields What is the impact? Mapping to a predefined choice list is not ideal because it requires us to manually update and map each tea...
Deepti Pradeep 4 months ago in Jira 1 Future consideration

When linking an Aha! record to an existing Jira record, perform a full sync of all fields

What is the challenge? When "Use Jira and overwrite Aha!" is selected, there is a full sync of all fields, allowing fields to update in Jira. But, when "Use Aha! and overwrite Jira" is selected, that same full sync is not performed, and one-way ...
Leigh Villalovos 9 months ago in Jira 0 Future consideration

Support mapping Asset object fields through Jira integration

Who would benefit? Customers using the Asset object through Jira Service Management. What impact would it make? When these Asset fields are added to Jira issue screens, this would allow users to map these fields to Aha! fields through the Jira int...
Stephanie Lechner about 2 years ago in Jira 0 Future consideration

Allow Jira Epics to Integrate

When creating Epics in Jira, they don't integrate into Aha. They will only integrate if you create child records under them that integrate into Aha. Epics need to be able to be integrated into Aha on their own.
Guest about 3 years ago in Jira 0 Future consideration

Jira integration - pre filter based on tag/field

Often there are items on a roadmap that do not require Engineering work. However when a release is sent to Jira (or over dev system) all the items under that release are also sent. This means that the down stream system can become full of items in...
Ann L about 4 years ago in Jira 0 Future consideration