Board View (based on Kanban) gives you the "big picture". Having tickets organized by column-stages allows you to see the workload, track progress and spot "bottlenecks" in your workflow easily.
Moving tickets from left to right, through the virtual "assembly line", makes it easy to track and visualize the progress.
There are many powerful features in Board View for a better workflow control:
- customizable column-stages — adjust your boards for your specific projects (see Workflow Designer)
- customizable team roles — who can edit what tickets and move them to what stage
- customizable tickets — define custom ticket fields to collect the data you need
- customizable ticket look — colors, tags, image covers, "star", plus adjusting what to show on them
- quick search-filter, including by custom fields
- filter by tags, ticket creator or an assignee
- archive tickets, to remove them from the board (they can be accessed via List View)
- collapse/expand columns to save space
- move tickets between boards for complex or forking workflows
- rearrange tickets by name, start date or deadline
People can easily adjust what and how they see it in the Board View. Teams can visually mark tickets with colors, tags or "stars". Tickets containing images will display them as a cover (optional). Columns can be collapsed to allow more space for important ones. You can define who can view or edit which tickets, or to what stage they can be dragged. For example, while a developer may drag a ticket to QA stage, only a manager may drag it to "Approved" stage.
If you are using custom fields, you can choose which ones to display in Board View:
For more control over what you want to see in Board View go to "Options" and selecte the "View" tab:
Ticket details — all the fields, the notes and files — are tracked in a separate Ticket View.
TIP: When dealing with very complex workflows with a large number of stages, you can split those stages between different project boards — "super-stages" of your workflow. Tickets then can travel not only inside one board, but also be moved to other project-boards. Since different teams can be responsible for different boards, it allows for a better work distribution. It also makes it possible to deal with parallel split workflows. For example, in a computer repair shop, the orders can come into the main board ("Order Entry") and after the case has been evaluated it could be sent either to "Hardware repair" board or 'Software repair" one (and even "bounce" between those two boards, if needed).