How to move work items between project area that contain a custom enumeration?
We want to move work items (non-bulk) between to project areas.
Normal attributes and standard enumerations (e.g. priority) for fine. Custom enumerations don't.
What may we doing wrong?
Background:
RTC version: 4.0.3
We have a ProjectArea for multiple months, created a process template out of it and created a new ProjectArea using this template.
The enumerations with "Storage = Process Specification" got copied (as expected)
The enumerations with "Storage = Database" didn't get copied (as expected), so we created them manually in the new ProjectArea making sure the technical ID is the same.
Creating a work item in the new ProjectArea works as expected, the enumeration values are complete.
Problem:
When triggering a move, the Eclipse client warns:
Problem wehen searching for corresponsing values in the target project area, these values will be omitted in the operation:
<Enumeration> not found: <Value>
I appreciate this warning in general. problem is: the enumaration value obviously exists. Any hints?
Normal attributes and standard enumerations (e.g. priority) for fine. Custom enumerations don't.
What may we doing wrong?
Background:
RTC version: 4.0.3
We have a ProjectArea for multiple months, created a process template out of it and created a new ProjectArea using this template.
The enumerations with "Storage = Process Specification" got copied (as expected)
The enumerations with "Storage = Database" didn't get copied (as expected), so we created them manually in the new ProjectArea making sure the technical ID is the same.
Creating a work item in the new ProjectArea works as expected, the enumeration values are complete.
Problem:
When triggering a move, the Eclipse client warns:
Problem wehen searching for corresponsing values in the target project area, these values will be omitted in the operation:
<Enumeration> not found: <Value>
I appreciate this warning in general. problem is: the enumaration value obviously exists. Any hints?
One answer
you said
>The enumarations with "Storage = Database" didn't get copied (as expected), so we created the manually in the new ProjectArea making sure the technical ID is the same.
that will confuse things. you THINK they are defined in the process area, but the project thinks they are defined in the database.
Comments
Here is what we did:
Workitem Type "Feature"
<customAttribute id="com.xyz.attribute.customer_mm" name="Customer" type="Cust_enum"/>
Create New Enumeration:
Name: Customer
ID: Cust_enum
Adding Enumeration Literals:
...
I suspect the enumeration literals got different IDs between the two PAs.
In the XML it's easy to check. Can that be done in the database, too?
Comments
sam detweiler
Jan 22 '14, 1:18 p.m.I think this is another limitation of Database stored enumerations.
Thorsten Gau
Jan 22 '14, 1:42 p.m.Addendum:
One Work Item type contains both process-spec and database based enumerations.
This has been mirrored in project area B.
Project Area A:
WorkItemType "Feature"
Enumeration Priority (Process Specification)
Enumeration Customer (Database)
Project Area B:
WorkItemType "Feature"
Enumeration Priority (Process Specification)
Enumeration Customer (Database)