We need to be able to manage our Features, grouping them into SPRINTS and then pushing the sprint and features into JIRA as a complete set, ie. creating the SPRINT and associated JIRA Tickets. Because the support for SPRINTS doesn't exist in Aha, the product managers are managing all their epics and related features in JIRA. Tying releases to sprints isn't a work-around because the PM would still need to go into JIRA, find all the tickets (features) and put them onto the appropriate sprint instead. Just too inefficient to get adoption internally.
|Release time frame||3 months|
Plan your work in sprints? If so, we have good news. You can now add a custom sprint field in Aha! and use it to map features to sprints in Jira.
Learn how to use Aha! and Jira together for sprint planning.