High Level Roadmap

Our Roadmap

Here is a high level of our roadmap for HuBoard over the remainder of 2016. Although things might move around a bit, this should more or less reflect our priorities this year (which are defined by our awesome community!)

Short Term

• Scrollable Columns

  • https://github.com/huboard/huboard-web/pull/280 . First iteration will affect the milestones view only. There is still discussion over whether the task view even needs column scrolling, or if huge task view columns are symptomatic of a greater problem.
  • Scrollable columns on the tasks view

• Card Redesigns

  • We hear you! There is so much relevant data for issues that we simply do not use... yet. We plan to overhaul HuBoard's cards in May, with simple changes like reducing the issue number size (too big!) and more complex changes like indicating what cards are linked to which. Leading to:

• Card Relationships

  • There is much demand for different types of relationships/interactions between cards, after building the underlying engine to make this possible, our first iteration will likely be linking issues to PR's (causing cards to 'merge' together)

• Dashboard -> Board UX

  • Our current set of error messages, warnings, and prompts for current and new users is pretty rough around the edges and we feel its about time to devote some real effort into making it better. More specific details coming later

• Milestone View Performance

  • Switching to a busy milestone view can be painful! We have identified the principle bottleneck affecting performance and will be greatly improving it.

Medium Term

• Card Relationships (extended)

  • Parent/Child relationships between cards, this would allow interesting visualizations for epics, and cascading ready or blocked statuses

  • Issue References, this is necessary because the current version of the GitHub API does not provide us the data we need to simply insert reference payloads into our issues

• Read-only access for non-github users.

• Epics huboard/huboard#674

  • Logical evolution to card relationships is Epic issues for High level planning and sub tasking

Longer Term

• Insights!

  • Right now the team is evaluating a myriad of options, but we would very much like to report on the interesting and useful data HuBoard + GitHub generates

• Backlog management

  • Bulk actions; move multiple cards at the same time
  • Table layout for large backlogs
  • Card decay, duplication detection, etc