Process Configuration Source change messed up my project
In RTC 2.0.0.2, eclipse client, I wanted to change several custom attributes from Boolean to a new enumeration (which gives me a 3rd "unassigned" option). Since the Eclipse Process Configuration GUI doesn't let me change the type of a custom attribute, I went into the Process Configuration Source and made the change manually. Seemed to work when I went back into the Attributes listing, but in the Editor Presentation, it complained that I couldn't display a Boolean attribute as an enumeration.
So, now, I tried to delete one of the custom attributes and start over. The attribute is definitely gone from the Custom Attributes list, and also does not appear in the Process Configuration source. However, the GUI does not allow me to add a new attribute with the same id, telling me that an attribute with the same id already exists. Lesson learned: don't muck with the source file. At this point, is there any way I can recover these, short of creating new attributes with slightly different id's? Thanks, Pete K. |
4 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Nov 24 '10, 2:23 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
It is my understanding that you can "hide" custom attributes by no
longer displaying them in the various displays, but you cannot either delete or change the type of a custom attribute because there may be instances of that custom attribute in the repository. Process team: please provide a correction if I got that wrong. Cheers, Geoff On 11/24/2010 12:53 PM, pkidwell wrote: In RTC 2.0.0.2, eclipse client, I wanted to change several custom |
I do not have a correction to that.
Perhaps someone from the Work Items team can give some guidance here. Is there a way to "unhide" a custom attribute? Will re-creating it in the source fix up the problem? Thanks, Martha Jazz Developer, Process Team It is my understanding that you can "hide" custom attributes by no In RTC 2.0.0.2, eclipse client, I wanted to change several custom:) |
Correct, don't muck with the source javascript:emoticon(':wink:')
We do not yet support to delete or change the type of a custom attribute. The attribute metadata (including its ID) is stored in the repository even if you have removed the custom attribute from a work item type definition. This is necessary because there may be work items that still use that custom attribute. But this prevents you from using the ID for a new custom attribute. I suggest that you first restore the attribute definition for the Boolean attribute (You can use the "Show in History" context menu action in the Process Configuration Source editor to restore a previous version). With this everything should work as before. Then you can introduce your new enum attribute (with new ID) and a new attribute presentation. Since only new work items will have this enum attribute, consider to upgrade all existing work items (how to: http://www-01.ibm.com/support/docview.wss?rs=3488&uid=swg21372230). With some queries and bulk actions move the Boolean data of old work items to the new enum attribute. Finally remove the Boolean attribute and the attribute presentation. hope that helps, --andre weinand Work Item Team I do not have a correction to that. It is my understanding that you can "hide" custom attributes by no In RTC 2.0.0.2, eclipse client, I wanted to change several custom:) :wink: :wink: :wink: |
Correct, don't muck with the source javascript:emoticon(':wink:') Well, that will teach me to try to cheat! Thanks, Pete K. |
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.