ADD A NEW IDEA

FILTER BY CATEGORY

My ideas: Jira

Showing 238 of 8090

Ability to map JIRA Team-field to a custom field in AHA

In integration 1,0 it was possible to map JIRA team field to a customfield in AHA, but in the new 2.0 integration that is't possible
Guest over 5 years ago in Jira 10 Future consideration

Notification when an integration is down

Would like to see some way of setting user(s) to be notified if there is an interruption in communication between integrated system.
Guest about 1 month ago in Jira 0 Future consideration

Move Aha! Requirements when linked JIRA Stories are Moved to a different Epic/Feature

The specific use case that this commonly occurs for is the following mapping: Feature = Epic and Requirement = Story; however, the same would apply to other mappings parent child mappings such as Story/Sub-task as well. Current behavior: The i...
Matt Case over 7 years ago in Jira 13 Future consideration

Complete Auto Import Functionality -- not just children of existing linked records

This is regarding the JIRA integration feature: Automatically Import New Records: Records will be imported automatically to Aha! from Jira. This applies to records which are created as children of previously linked initiatives, releases, mast...
Guest over 4 years ago in Jira 4 Future consideration

Sync goals to Jira

We manage the high level roadmap in Aha and the day to day development in Jira. Keeping them in sync is easy with the Jira integration, but we do like to filter the Jira epics by the Aha goals. Right now, to be able to track dev progress against g...
Guest over 2 years ago in Jira 2 Future consideration

Show required fields in integration mapping

When setting up an integration, it would be helpful to have a way to be prompted to map required fields in Jira. Currently, it is possible to create an integration that does not have field mappings for required fields in Jira. This causes the inte...
Madeleine Black 12 months ago in Jira 1 Future consideration

Do not allow requirements to be mapped without a Links To relationship set

It is possible to create an integration where you have requirements mapped to a Jira record type, and where you have no Links To relationship established to a parent record in Aha! This results in import errors where requirements cannot be importe...
Madeleine Black 12 months ago in Jira 0 Future consideration

Handle multiple FixVersions in JIRA

An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix v...
Danny Archer almost 8 years ago in Jira 15 Future consideration

Integrating with a specific Jira board

It would be helpful if we could use the Jira integration to send features to a specific board. We have several dev teams working within a single project, but they utilize different broads. We would like to send a feature to open a record is a spec...
Reut Levi about 1 year ago in Jira 1 Future consideration

Filter noise from Jira integration logs

The log file currently reports on Jira tickets that are out of scope for the integration (e.g., bugs, stories, tasks) as defined by the integration template. These log entries typically end with "No changes made in Aha!" If I'm trying to find the ...
Sandy Kobayashi 7 months ago in Jira 0 Future consideration