RELATED IDEAS
Provide the ability to map multiple ticket types to requirements
We are hooking Features into Epics, and discussing with development and the rest of the product team, the individual enhancements, new features, and tasks that are required to be performed for the "Epic" to be completed. Aha/Jira integration only allows mapping one type of ticket into requirements, where we'd need a few different types since Development makes these tickets from Jira.
-
ADMIN RESPONSEJun 18, 2016
The best way to achieve this would be to create multiple integrations. As you had noted, each integration allows for 1 mapping. By creating multiple integrations, you can send your features/requirements to JIRA via the correct integration set up.
© 2024 Aha! Labs Inc.•All rights reserved
Hi Puneet, this article explains this use case in more detail. If you need additional guidance, please contact support@aha.io. Thank you!
huh, what? How is that going to help? How would I push a release to Jira over multiple connections?
How do you set up multiple integrations in the same project?