It's all about the answers!

Ask a question

Titlebar for custom workitems - Summary only?


Ernest Crvich (19211918) | asked Jan 26 '12, 12:42 p.m.
I notice that the title bar of my test custom workitem says "<untitled>". By default, RTC seems to use the Summary field value for the titlebar text. How do I change that to use a different field's value for the title text? I have no use for the Summary field in most of my custom work items.

3 answers



permanent link
Geoffrey Clemm (30.1k23035) | answered Jan 28 '12, 5:08 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Is there a reason you can't just have the field that you want to appear
in the title be the Summary field (instead of defining some custom field
for it)?

Cheers,
Geoff

On 1/26/2012 12:53 PM, crvich wrote:
I notice that the title bar of my test custom workitem says
"<untitled>". By default, RTC seems to use the
Summary field value for the titlebar text. How do I change that to
use a different field's value for the title text? I have no use for
the Summary field in most of my custom work items.

permanent link
Ernest Crvich (19211918) | answered Jan 30 '12, 1:10 p.m.
Is there a reason you can't just have the field that you want to appear in the title be the Summary field (instead of defining some custom field for it)?

In some cases, yes, and that's what I've done in the meantime, but this forces the attribute to be a Small HTML type (which may not be appropriate for the main/identifying piece of data in the work item) and also adds obfuscation by making our internal scripts reference an attribute name (Summary) that has nothing to do with the data it contains (e.g., RetainComponent). I realize the label on the presentation can be anything, but it's an annoying kludge for the scripts.

We have about 20 custom work items for our product (most of which have several associated scripts), so once we go down this road of fudging the attribute name we're effectively going to be stuck with it forever. But I'm guessing from your reply that Summary is indeed hardcoded in RTC as the identifying data.

permanent link
Geoffrey Clemm (30.1k23035) | answered Jan 30 '12, 2:53 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes, that is my understanding.
In general, I actually believe it is the right approach to motivate
users to re-use the standard fields, since this will make generalized
querying more feasible. So even if "title" isn't the name you would
pick for this field, having every schema use "title" as its "title-like"
attribute makes it more feasible to eventually support general queries
for work items with a given title.

Cheers,
Geoff

On 1/30/2012 1:23 PM, crvich wrote:
gmclemmwrote:
Is there a reason you can't just have the field that you want to
appear in the title be the Summary field (instead of defining some
custom field for it)?

In some cases, yes, and that's what I've done in the meantime, but
this forces the attribute to be a Small HTML type (which may not be
appropriate for the main/identifying piece of data in the work item)
and also adds obfuscation by making our internal scripts reference an
attribute name (Summary) that has nothing to do with the data it
contains (e.g., RetainComponent). I realize the label on the
presentation can be anything, but it's an annoying kludge for the
scripts.

We have about 20 custom work items for our product (most of which have
several associated scripts), so once we go down this road of fudging
the attribute name we're effectively going to be stuck with it
forever. But I'm guessing from your reply that Summary is indeed
hardcoded in RTC as the identifying data.

Your answer


Register or to post your answer.