Effects of changing the values in an enumerated attribute
Hi,
I would like to add a 'category' field to a work item type in a
customized process template. I would like it to be a drop down list of
possible values (there are only 4). So I have defined a new enumeration
in the process configuration and use a presentation of kind
com.ibm.team.workitem.kind.enumeration to represent it as a drop down list.
Once I have released v1 of the project I would like to change the values
users can choose for v2 of the project, but I don't want the values in
the category of the v1 work items to change. If I replace the values in
my enumeration in the process configuration when we start v2 will this
just work - i.e. the v1 work items retain their existing category
values? I'm hoping the values are stored as a string in the db rather
than (say) an integer form of the enumeration.
Many thanks,
Jeremy
I would like to add a 'category' field to a work item type in a
customized process template. I would like it to be a drop down list of
possible values (there are only 4). So I have defined a new enumeration
in the process configuration and use a presentation of kind
com.ibm.team.workitem.kind.enumeration to represent it as a drop down list.
Once I have released v1 of the project I would like to change the values
users can choose for v2 of the project, but I don't want the values in
the category of the v1 work items to change. If I replace the values in
my enumeration in the process configuration when we start v2 will this
just work - i.e. the v1 work items retain their existing category
values? I'm hoping the values are stored as a string in the db rather
than (say) an integer form of the enumeration.
Many thanks,
Jeremy
One answer
Once I have released v1 of the project I would like to change the values
users can choose for v2 of the project, but I don't want the values in
the category of the v1 work items to change. If I replace the values in
my enumeration in the process configuration when we start v2 will this
just work - i.e. the v1 work items retain their existing category
values? I'm hoping the values are stored as a string in the db rather
than (say) an integer form of the enumeration.
Enumeration literals have an ID, a label and (optionally) an icon. The
ID is stored in the work item.
So when you change the labels, you will see the new labels also for the
v1 work items.
When you change the IDs, the v1 work items will still refer to the old
IDs. But there will be no labels or icons anymore in the UI for the v1
work items, just the ID. We don't recommend this approach.
Maybe you could introduce a new attribute and enumeration in v2 for your
purpose and change the type and presentation configuration accordingly?
Patrick
Jazz Work Item Team