Board View mode

There are four ways of data visualization in Targetprocess 3: Board view, Detailed view, List view, and Timeline view. Once you have configured your view, you can quickly switch between all these modes to choose the most suitable one.

Board is a core concept in Targetprocess 3. With boards you can extract, present and group data using vertical and horizontal lanes (Columns and Rows).

You can swap vertical and horizontal lanes really fast, visualizing the same data in a different way. Moreover, you can set filters for the lanes. For example, you've created a board that shows user stories grouped by features. There are quite many features, but you need to see just the open features. You can quickly create a filter showing only the open features in rows.

Let's work with a user story entity (card). You can create quite many boards, each highlighting a certain property. So, you've chosen user stories as cards and now you're selecting a vertical lane. Here are the choices:

  • Iteration: it will be an iteration plan. You will see the upcoming iterations, and you will be able to move stories to these iterations.
  • Release: a release plan.
  • State: a kanban board.
  • Priority: a priorities board where you can set business values for user stories with drag and drop.
  • Effort: an estimation board where you can quickly change effort for user stories.
  • Feature: a story map that will help you create backlog with features and user stories quickly.
  • Person: a work-by-person board.
  • Project: user stories broken down by projects.
  • Team: user stories broken down by teams.
  • Tags: tags are very flexible, so you can do very interesting things with this board.
  • Custom Field: you can group user stories by any custom field you've created. The applications are limitless.

That's the diversity we have with just one swimlane. But you can tune both horizontal and vertical lanes. Now imagine how many boards you can create. Thousands of them.

See Also

  • Alex Porter

    Is there a way to stop kanban boards from grouping the initial state when there are two entities included?

    I have the initial state for bugs set at “Ready for Dev” because I expect them to be logged with enough detail that a developer could pick them up anytime if they’re out of work, even if they’re not “Prioritized for Dev”. However, on my board, they’re getting lumped into a “To Do” column with User Stories in a “Backlog” state rather than being put in the “Ready for Dev” state column.

  • Natalia

    Hi Alex,
    I’m afraid there is not way to stop initial states from grouping. Let explain how states grouping currently work in targetprocess. There are 3 states in the workflow which have special meaning:
    1. Initial – the first one;
    2. Planned. After this state the item is considered ‘work-in-progress’. Moving to the any subsequent state sets Start date, which affects cycle time.
    3. Final – the last one. The work is considered to be done. Moving to this state sets Completion Date.

    And these are two rules how the states are groups on boards:
    1. All Initial states are grouped together. Same works for Planned states and for Final states;
    2. All the rest are grouped by name.

    That is why Ready for Dev initial state of bugs can’t be merged with ‘not initial’ Ready for Dev state of stories.

  • Martin Montalbetti

    is there a way to add colors or paint a User Stories

  • Natalia

    Hi Martin,
    You can use Visual Encoding to color cards. See the article for the details:

Still have a question?

We're here to help! Just contact our friendly support team

Find out more about our APIs, Plugins, Mashups and custom extensions. Join our community of passionate users and even discuss directly with our developers.