Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

RTC4 Work Item Result Set: Unable to right-click and edit a field

When using the RTC3 eclipse client, I could, for example, run a defect query, see the results of the query, and then right-click on many of the fields, and get the "Change ..." menu item, and I could change the value. For example, we have customized several new attributes that were enums, and I could easily and quickly change the value to another enum.

I used to be able to do that with RTC3.  We moved our server to RTC4, and after I upgraded my RTC client to RTC4, I could no longer perform the same edit as described above (right-click in the Work Item result set view).  (If I used my old RTC3 client connected to the RTC4 server, I CAN edit the values like I described above).

This is a productivity impact.  I need to query for and display lots of defects, and quickly change values, either quickly one at a time, or multiple select and change a batch of them to the same value.

Is there something I can configure to allow this to work using the RTC4 client?

0 votes



2 answers

Permanent link
Chris,
I see that some attributes can be modified.  Most are the 'built-in' or if custom a simple type (integer, string, etc).  Custom enumeration related attributes don't seem to offer the ability to change attribute from the work item list.

My RTC is 4.0.1

Kevin

0 votes

Comments

And if we're looking at your "usual" project area, at least 2 work item types (Defect/Story) have multitude of work items w/o all configured attributes.  I don't know if this is a factor in the work item table behavior; just making the point.

Thanks for the ideas.... It wasn't a factor with the RTC3 client.  Even for brand new defects, I'm unable to edit the customized attributes, from the Work Item Result Set view.  Really need this ability.  I really don't want to have to "hold on" to the RTC3 client in order to do this.  Any other ideas anybody?


Permanent link
Does anybody know if this is considered a bug with RTC 4 client?  Should a bug be opened for this?  It worked in RTC 3 client, but not in RTC 4 client; sorta sounds like a bug.

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 12,021

Question asked: Mar 28 '13, 2:47 p.m.

Question was seen: 2,862 times

Last updated: Apr 08 '13, 10:46 a.m.

Confirmation Cancel Confirm