[SOLVED] Colorize help with Categories/Team Areas
I am unable to get the colorize to work. I have tried the following:
category:"Info Service"
category:'Info Service'
category~"Info Service"
category~'Info Service'
The plan is owned by the team area "Info Service"
The Team Area "Info Service" is a sub-team.
category:"Info Service"
category:'Info Service'
category~"Info Service"
category~'Info Service'
The plan is owned by the team area "Info Service"
The Team Area "Info Service" is a sub-team.
Accepted answer
I have looked at one of the latest builds for the next release.
"Category" is not a field that can be colorized. However it is possible to colorize "filedAgainst". I got:
filedAgainst:JKE
filedAgainst:BRM
with JKE and BRM being the display name of the category.
"Category" is not a field that can be colorized. However it is possible to colorize "filedAgainst". I got:
filedAgainst:JKE
filedAgainst:BRM
with JKE and BRM being the display name of the category.
5 other answers
I have looked at one of the latest builds for the next release.
"Category" is not a field that can be colorized. However it is possible to colorize "filedAgainst". I got:
filedAgainst:JKE
filedAgainst:BRM
with JKE and BRM being the display name of the category.
I have created a bug for this because the help system references the use of Category directly. Bug number id Defect 212628.
Help screen that is wrong is here, https://jazz.net/help-dev/clm/topic/com.ibm.team.apt.doc/topics/r_quick_query_syntax.html
Thanks.
Just for interest's sake, I tried this out with the 4.0RC3 build .. and filedAgainst is a defined field (in the WebUI), but I'm getting no colored markings in my plan items. Other fields like "priority" are colorizing just fine. Has anyone else had a problem with this in the 4.0 builds, or is it just me?
Cheers,
Geoff
Cheers,
Geoff
I have looked at one of the latest builds for the next release.
"Category" is not a field that can be colorized. However it is possible to colorize "filedAgainst". I got:
filedAgainst:JKE
filedAgainst:BRM
with JKE and BRM being the display name of the category.
I experienced the same with RC0. The interesting part though, is that when I tried to colorize through eclipse it does work in both clients (Web UI & Eclipse). I filed a defect for this:
https://jazzdev.torolab.ibm.com:9443/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=212719
--
Gabriel Enriquez, IBM Rational, Tracking & Planning
https://jazzdev.torolab.ibm.com:9443/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=212719
--
Gabriel Enriquez, IBM Rational, Tracking & Planning
Just for interest's sake, I tried this out with the 4.0RC3 build .. and filedAgainst is a defined field (in the WebUI), but I'm getting no colored markings in my plan items. Other fields like "priority" are colorizing just fine. Has anyone else had a problem with this in the 4.0 builds, or is it just me?
Cheers,
Geoff
I have looked at one of the latest builds for the next release.
"Category" is not a field that can be colorized. However it is possible to colorize "filedAgainst". I got:
filedAgainst:JKE
filedAgainst:BRM
with JKE and BRM being the display name of the category.
Just for interest's sake, I tried this out with the 4.0RC3 build .. and filedAgainst is a defined field (in the WebUI), but I'm getting no colored markings in my plan items. Other fields like "priority" are colorizing just fine. Has anyone else had a problem with this in the 4.0 builds, or is it just me?
Cheers,
Geoff
I have looked at one of the latest builds for the next release.
"Category" is not a field that can be colorized. However it is possible to colorize "filedAgainst". I got:
filedAgainst:JKE
filedAgainst:BRM
with JKE and BRM being the display name of the category.
I just tried this with an RC4 system. After I selected "filedAgainst:" from the drop down, it suggested "filedAgainst:BRM" and selecting that got me color tags after clicking OK on the edits. This was using the Sprint and Release backlogs for the JKE sample. It's a potentially uninteresting use case since the Plan is scoped against "Filed Against" already.