Color and sort by tree relationship property

Apr 30, 2008 4:54am

Koen De Hondt 56 post(s) #1409

Use case: a scrum team works on 3 projects in parallel. In each sprint they plan stories for the 3 projects. They use a planning tree Release > Sprint > Story. The team likes to do sprint planning with a grid view that has a lane per sprint and one lane with stories of which the sprint is set to “(not set)”. In that grid view, they want to color the cards according to projects they belong to, so that they can easily identify them.

This use case is not supported in Mingle 2.0, because the tree relationship properties are not included in the list that appears when clicking the “Color and Sort by:” combobox, and because it is impossible to assign colors to the values of the relationship properties (i.e. cards).

Mingle supports colors for values of managed lists (i.e. finite sets of values). In theory, tree relationship properties have an infinite set of values, so assigning a color is not possible. But in practice, many of the relationship properties in the upperlevels of trees (such as releases, sprints, epics, features, ...) have a small set of values. So I wonder whether it makes sense to support assigning colors to those. For instance, if it would be possible to assign colors to cards, Mingle could allow coloring cards in the grid view based on the color of the card that is the value of a relationship property. For the given use case above, the 3 project cards would have colors A, B and C. In the grid view, it would be possible to select “Color and Sort by: Project” and the cards in the grid would have a colored stripe A, B, C or none.

May 3, 2008 8:48pm

David Pattinson 76 post(s) #1441

It seems reasonable that if you were able to select a relationship property for “Color and Sort by”, then the values for that relationship property which are currently in the view could be listed to have a color assigned. It doesn’t make sense to consider color for values that are not in the view anyway, and this color assignment could be temporary and only persist for the lifetime of the view, getting around the issue of an unbounded possible set of values.

May 5, 2008 1:23am

Koen De Hondt 56 post(s) #1444

David,

You are right. Many values are used for a period of time (sprints, projects, ...) and therefore the unused values do not need an associated color anymore.

Aug 18, 2008 2:52pm

Adrian Wible 32 post(s) #2139

+1 on being able to color and sort by tree relationship properties (e.g. iteration card)

Sep 23, 2008 11:20pm

phatmann 10 post(s) #2374

+1 for being able to sort on any relationship or dynamic card property (like Owner). Furthermore, provide option to display the property value right on the card, as a supplement or replacement for color. The property value could replace the ID #.

Color and sort by tree relationship property#576

Voices

Apr 30, 2008 4:54am Koen De Hondt 56 post(s) #1409	Use case: a scrum team works on 3 projects in parallel. In each sprint they plan stories for the 3 projects. They use a planning tree Release > Sprint > Story. The team likes to do sprint planning with a grid view that has a lane per sprint and one lane with stories of which the sprint is set to “(not set)”. In that grid view, they want to color the cards according to projects they belong to, so that they can easily identify them. This use case is not supported in Mingle 2.0, because the tree relationship properties are not included in the list that appears when clicking the “Color and Sort by:” combobox, and because it is impossible to assign colors to the values of the relationship properties (i.e. cards). Mingle supports colors for values of managed lists (i.e. finite sets of values). In theory, tree relationship properties have an infinite set of values, so assigning a color is not possible. But in practice, many of the relationship properties in the upperlevels of trees (such as releases, sprints, epics, features, ...) have a small set of values. So I wonder whether it makes sense to support assigning colors to those. For instance, if it would be possible to assign colors to cards, Mingle could allow coloring cards in the grid view based on the color of the card that is the value of a relationship property. For the given use case above, the 3 project cards would have colors A, B and C. In the grid view, it would be possible to select “Color and Sort by: Project” and the cards in the grid would have a colored stripe A, B, C or none.

May 3, 2008 8:48pm David Pattinson 76 post(s) #1441	It seems reasonable that if you were able to select a relationship property for “Color and Sort by”, then the values for that relationship property which are currently in the view could be listed to have a color assigned. It doesn’t make sense to consider color for values that are not in the view anyway, and this color assignment could be temporary and only persist for the lifetime of the view, getting around the issue of an unbounded possible set of values.

May 5, 2008 1:23am Koen De Hondt 56 post(s) #1444	David, You are right. Many values are used for a period of time (sprints, projects, ...) and therefore the unused values do not need an associated color anymore.

Aug 18, 2008 2:52pm Adrian Wible 32 post(s) #2139	+1 on being able to color and sort by tree relationship properties (e.g. iteration card)

Sep 23, 2008 11:20pm phatmann 10 post(s) #2374	+1 for being able to sort on any relationship or dynamic card property (like Owner). Furthermore, provide option to display the property value right on the card, as a supplement or replacement for color. The property value could replace the ID #.