The Team Board can easily be customized to better fit your development workflows.

Behind each board column is a Data Explorer query pulling issues and pull requests matching specific criteria. This is how the Team Board automatically updates itself based on the progress of your team. The query filters can of course be customised to show/hide certain items based on labels, assignees etc.

How to edit the board?

First click on the Edit Board button. This button is only visible if you are a Team admin.

Clicking this button will bring the board edit screen:

The edit view allows you can take a few structural actions:

  • Preview tab (top left): it allows you to see what your current changes look like before actually saving them for the whole team.

  • Cancel/Save (top right): revert your changes or save them. Saving the board will publish the new version to the whole team.

  • Move up / Move down / Delete (left side of each row): the caret icons allow you to re-arrange the order of columns and the bin allows you to simply delete a column.

  • Add column (bottom): allows you to add more columns to your board. Boards are currently limited to 10 columns.

You can expand a specific row by clicking on it. This will reveal the filters used to define that board column and allow you to rename it:

Feel free to add or remove columns and modify each column's filters to better suit your development workflow.

ProTip 1: I've messed up with the board...what can I do?

If at any point you feel you've messed up too much with the board - it happens to the best of us - here is what you can do.

If you haven't saved the board yet

Click Cancel (at the top left) then Edit Board again to start fresh from the default board.

If you have already saved the board

Click Edit Board then Reset to default then Save.

ProTip 2: do not hardcode users in filters

Unless you have a very specific use case in mind we recommend not adding any filter related to a specific user (e.g. author = bob).

You must ensure the column filters make sense at a Team level and user level to be compatible with the View as selector.

ProTip 3: use relative time filters instead of hardcoded dates

If you look at the definition of the default Done column, you'll notice we use a relative time filter to retrieve items that were closed within the last three days.

Using relative time filters is a good way of ensuring your board remains dynamic. On the contrary, using hardcoded dates would require you to frequently update your board to ensure that the definitions stay up to date.

You feel you're missing a specific time filter to get that board shinier? Feel free to ping us on chat.

ProTip 4: use mutually exclusive filters

Board columns are stateless and are not aware of the other columns' filters. Therefore if an item matches the filters of two columns, it will appear in these two columns.

Generally speaking it is best to ensure your column filters are mutually exclusive if what you are looking for is a progressive board (items move from left to right).

There are cases though where having overlapping columns can be beneficial. Let's consider the case of two columns called Todo and Todo (Urgent):

  • Todo: Displays all issues currently assigned

  • Todo (Urgent): Display all issues currently assigned and having the label "urgent"

By doing so, not only will you have visibility on Todo and Todo (Urgent) issues but having the two columns side by side will also provide a visual indication of the proportion of urgent issues amongst todo issues. Overlapping isn't always bad 😺.

Did this answer your question?