Please add the concept of "Sprints" separate from "Releases"

Please indulge me be allowing me to start off with some definitions.

Sprints are generally 1-3 weeks long, happen at a regular cadence and don't have anything to do with ongoing projects/releases other than the fact that Stories related to a project are added to a Sprint.

Projects have phases and milestones, can span multiple sprints and can be Gantt charted easily within Aha.

The problem is, Aha treats Sprints and Projects as the same thing. They are not and when I add Releases for project planning purposes, those releases get confused with my Sprint releases making a mess of my Board.

Proposed solutions:

  1. Add a concept of a Sprint to Aha, separate from Releases
  2. Add phases to Epics ("Master Features") and allow for more roadmapping features
  • Guest
  • Oct 10 2019
  • Already exists
Release time frame
  • Oct 11, 2019

    Admin Response

    Thank you for the idea and taking the time to explain it well!

    Because Aha! is so flexible, there are a number of ways to represent sprints in Aha!, as separate from releases. This article goes into detail on the option of using a custom field and syncing that with Jira.

    I encourage you to reach out to our customer success team at support@aha.io and they will get back to you quickly to work through some options that might work well for you.

  • Attach files
  • Guest commented
    11 Oct 18:04

    Here's the thing - So, what you're telling me is to do my Sprint planning in JIRA?

  • Admin
    Kelly Sebes commented
    11 Oct 19:30

    The Jira integration can sync sprints from Aha! to Jira and Jira to Aha!, allowing you to assign items to sprints from either tool.