iceScrum | Coloring of tasks under Planing – iceScrum

iceScrum Forums Discuss on iceScrum

Viewing 2 posts - 1 through 2 (of 2 total)

  • Author
    Posts
  • #198544

    r09491
    Participant

    I have created a FEATURE with a distinct color. If I allocate STORIES to the FEATURE they get the same color. The STORIES have tasks. I am surprised that they do not inherit the colour of their STORY. Is this a bug or a feature? What is the rationale for the feature?

    #198591

    Nicolas Noullet
    Keymaster

    Hi,

    The point of Feature color is to help visual management when dealing with stories. This allows the human mind to take a shortcut and categorize stories automatically, which is really handy when dealing with dozens of stories which are displayed in the same backlog.

    Tasks would not benefit that much from in turn inheriting this color. Indeed, unlike stories that don’t show their feature explicitly, tasks are grouped by story in the task board and the story name is displayed. The feature color is also already visible (left border of the row). Finally, unlike features and stories which are both business items, tasks are technical items so it can be useful to leverage visual management to classify them according to technical criterias rather than business ones. For example, for the development of a client/server application you can pick green for tasks dealing with frontend development and blue for the backend.

Viewing 2 posts - 1 through 2 (of 2 total)

The forum ‘Questions and help’ is closed to new topics and replies.