Colorize only works on first WI

Mark Ingebretson wrote:

We have a release plan we're viewing in Backlog mode. There are a few
colorize expressions that have been entered. With Status:In Progress,
it colorizes the first Epic with that status, but none of the other In
Progress epics are colorized. We've tried double quotes around the "In
Progress", but I believe that removed the color from the one epic.

Any ideas on why colorize would only work on the first work item in the
plan?

I can create a query with those parameters (type=Epic, status=In
Progress, that iteration), and it finds 18 work items, and the release
plan shows those 18 work items.

Can you pls post a screen shot of your colorize expressions? If I user
the following, Epics that are in progress are colored: 'state:"In
Progress" type:Epic'

You might have a second colorize expression that matches and overrules
the coloring for the other epics?


--
Cheers, Johannes
Agile Planning Team

During further investigation we found that the state expression works in the web ui, but seems to be broken in the rich ui.
We've opened defect 90986 (https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/90986)

--
MikeS
Jazz Agile Planning team

Johannes Rieken wrote:

Mark Ingebretson wrote:
We have a release plan we're viewing in Backlog mode. There are a few
colorize expressions that have been entered. With Status:In Progress,
it colorizes the first Epic with that status, but none of the other In
Progress epics are colorized. We've tried double quotes around the
"In Progress", but I believe that removed the color from the one epic.

Any ideas on why colorize would only work on the first work item in
the plan?

I can create a query with those parameters (type=Epic, status=In
Progress, that iteration), and it finds 18 work items, and the release
plan shows those 18 work items.

Can you pls post a screen shot of your colorize expressions? If I user
the following, Epics that are in progress are colored: 'state:"In
Progress" type:Epic'

You might have a second colorize expression that matches and overrules
the coloring for the other epics?

Michael Schneider wrote:

During further investigation we found that the state expression works in
the web ui, but seems to be broken in the rich ui.
We've opened defect 90986
(https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/90986)

Hi Michael and Johannes,

I see the same results in both the web and rich clients.

I've attached a screenshot of the expressions, at least one of the
versions I tried.

Here's what I'm seeing in both the rich client and web client.

Status:In Progress - only the first epic colorized
Status:"In Progress" - no colors (I know this is the correct way per
the help)
Status:"In Progress" type:Epic - all Epics colorized regardless of
Status value

If I add a second expression, 'status:Done type:Epic', that over-rides
the first one, and I see all epics with the second color. I've tried
both "Status" and "status". This is with a modified version of Scrum 2.0.

Thanks!

Hi Mark

we fixed defect 90986 for this week's 2.0.0.1 RC1 build. use the "state" quick query attribute to colorize (you tried "Status").
The fix for defect 90986 also enables proper code completion in the rich client for the "state" attribute. (see http://www.poshnet.ch/jing/2009-08-25_1440.png)

Status:In Progress - only the first epic colorized

due to the missing quotes, the query is interpreted as two conditions: "Status:In" and "Progress". The first condition is ignored as there's no "Status" quick query attribute, the second matches work items where the summary and or description contains the word "Progress". That is why a work item was
colored.

Status:"In Progress" - no colors (I know this is the correct way per
the help)

The condition is ignored as there's no "Status" quick query attribute, therefore no work items are colored

Status:"In Progress" type:Epic - all Epics colorized regardless of
Status value

Again, the first condition is ignored as there's no "Status" quick query attribute, therefore all epics are colorized

--
MikeS
Jazz Agile Planning team

Michael Schneider wrote:

Hi Mark

we fixed defect 90986 for this week's 2.0.0.1 RC1 build. use the "state"
quick query attribute to colorize (you tried "Status").
The fix for defect 90986 also enables proper code completion in the rich
client for the "state" attribute. (see
http://www.poshnet.ch/jing/2009-08-25_1440.png)

Hi Mike,

Thanks for your note.

I switched our expressions to use state: and now have colorization in
the web client only. We had extra trouble developing this since we were
doing it in the rich client. Now we know why. Thanks for your help!