ADD A NEW IDEA

FILTER BY CATEGORY

Jira

Showing 232

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 almost 7 years ago in Jira 13 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 9 months ago in Jira 1 Future consideration

Add 2-way integration mapping for release start and end dates

Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release. Now that this date is set manually, it should be poss...
Austin Merritt about 3 years ago in Azure DevOps Services and Server  / Integrations / Jira / Rally 1 Future consideration

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 about 5 years ago in Jira 9 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 almost 2 years ago in Jira 2 Future consideration

Provide applicable error message when a Jira integration can't authenticate due to a captcha challenge issue

When attempting to set up a Jira integration, authentication can fail with a 403: CAPTCHA_CHALLENGE error we can see in the logs, but there is no applicable message on the integration-set up screen. It just says "We could not connect to your Jira ...
Emily Yankush about 1 month ago in Jira 0 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 about 4 years ago in Jira 4 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 over 7 years ago in Jira 12 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 5 months ago in Jira 0 Future consideration

Project level automation with Jira

Requesting a change to Aha! Jira integration to allow for project level automation. Project level webhooks send payloads differently than system level payloads. If support for project level webhook payloads were added, we could enable multitudes o...
Guest 7 months ago in Jira 0 Future consideration