Add sprint by sprint epic view

[delaurentis]

Planner is currently a helpful tool for rallying a team around tactical goals for the next few sprints, but it isn't too helpful with the longer strategic goals (epics). Here are some initial thoughts on how to add strategic capability.

Epic List Page

• Planner has the concept of Cards and Listings, and it's interesting to think about how that might work with epics.
• For issues: Cards = Milestones, Listings = Issues
• For epics, we have a few options:
  • Cards = Quarters, Listings = Epics, long epics may be repeated
  • Cards = Years, Listings = Epics, epics on boundary may be repeated
  • Cards = Parent Epics, Listings = Epics, need horizontal space for wide sprint selector
• The epic listings could have a sprint selector, similar to the current day selector on the schedule tab

The Epics list could have multiple extra columns options, including:

• Schedule (sprint by sprint)
• Issue Stats (counts of different statuses or priorities)
• People (people assigned to the epic)
• Labels

Epic Drilldown Page

It would be nice to have the ability to easily create issues within epics, or see all issues within epics. This means we'd ideally have an epic view that you could drill to. It would focus on just 1 epic, and show a list of all issues, and offer the ability to add new issues to that epic.

We'd need a new URL for this page, and some way of showing you are there in the top filter bar.

Extra columns for this page could include a Sprint (the single chip version) and Assignee. These could be combined into a single view for quick assignment of issues to people / sprints. It could also add extra sprint labels to the epic. Although we wouldn't want to ever remove them, since we should be able to forecast a larger epic before adding detailed tickets.

Data Storage

We can't associate milestones or multiple assignees with epics. We could get all this info from the associated tickets, but there is a chicken and the egg issue. During strategic planning, which can happen months in advance of detailed ticket planning, we want to create the epics and allocate resources.

We could use a few techniques here:

• Labels for multiple milestones, similar to how we do days of the week for issues.
• Labels for assignee names
• A marquee issue associated with the epic that has assignees
• Store information (assignee usernames + milestones) in the epic's description and parse it out each time
• OR use an outside DB for creating / storing epics