Agile board feedback

Hello Andy,

You can already narrow down issues shown on the board:

• You can filter stories using a search query in the search box. E.g., type in "priority: Critical, Major" to see only critical and major issues (features/tasks/bugs/etc.) on the board.
  
• To configure number of shown columns (to narrow a "wide" board), open board's Settings and select only those states that you wish to see.

As for the color coding, it's probably a good idea, though we definitely won't be considering its implementation before the upcoming release.

What do you mean by "story epics"? Could you please provide more details?

best regards,
kate

Hi,

A story epic or story feature is typically a large story that can be broken down into smaller stories but still grouped under the epic. You see similar features in other software such as Rally and Pivotal etc.

Story epics are explained here - http://www.agilemodeling.com/artifacts/userStory.htm#Epics

Colour coding/grouping should I would argue really belong in this feature. It is a common visual system that teams use colours as a 'first glance' system to indicate

Projects as the flow across the board
Status of stories - for example stories that are blocked etc.

Loss of these colours would drive a team back to a manual board and away from using YT so I would argue that it makes sense that you don't take away.

Thanks

Andy

Agreed, epics (parents of stories) are critical to us.  Currently the board only supports two levels - parents and subtasks.  (Parents as swimlanes).

Another vote for epic stories.

I think that in a perfect world the number of levels could be set / Agile Board. We're currently running one Agile Board for a couple of sub-projects spanning over 5 development centers in 5 different countries and the umbrella project have 4 levels...

Another vote from me. I raised this issue under the heading "Combined Task Board" here, but I think the idea of epic support is essentially the same. I now have 10 projects and there's no way to get an overview.

One of the major benefits of Kanban + Cumulative Flow diagrams is that you can more easily identify bottlenecks. How great would it be to identify a bottleneck source which keeps reoccurring across projects?

Following up on the usage of a three-tiered board in YouTrack, similar to the way Jira and other agile boards are now configured. With Epics – User Stories – Tickets, as a three level view. Are there any plans for this to get added to the YouTrack boards?