Skip to Main Content

Free trial
Join a demo

Share your product feedback

Ideas
Resources
Polls

Resources
Polls

Log in / Sign up

Please enter your email address

Home
A-I-9805
A-I-9950

Add a new idea Subscribe

2 VOTE

Status Future consideration

Categories Jira

Created by Dale Potter

Created on Oct 28, 2020

RELATED IDEAS

Jira Integrations: Map Aha Releases to a custom Jira Version Field
JIRA integration: support mapping of “Release name” into custom field
bi-directional epic status mapping with Jira
Allow for two-way mapping to Jira with Initiatives
When importing records from JIRA, allow Aha! to overide the directionality of fields configured in the integration
Ability to update Jira Affects Versions field from Aha via integration
Map custom release field in Jira integration
Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with
Provide the ability to map the Release field from a Feature or Epic to an external system such as ADO
Allow features to span across releases for better data model alignment between Aha and JIRA

Support bi-directional flow of data when mapping Aha! releases to Jira sprints as a field mapping for features

Use case:

Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.

Attach files
Enter a subject
Drop here to upload

Idea management by

Aha!

Create your own ideas portal to crowdsource feedback

Products
Company
Resources
Popular links
Contact us

© 2025 Aha! Labs Inc.•All rights reserved

Privacy policy
Terms of service