Attribute 'cardinality' of 'role-definition'
There are two possible values for "cardinality" (single and many) in the "role-definition" tag.
I would like to know what are the differences between these values (single versus many) ? |
3 answers
If you specify 'single' then you are indicating that this role will be
assigned to exactly 1 contributor at any point in time. For example, you might define a floating role such as the 'build-engineer' which is assigned to the contributor on the team that is playing that role for some period of time. If you specify 'many' then you are indicating that this role may be assigned to multiple contributors. For example, you might define a 'documentation' role which is assigned to all members of the team who are documentation writers. -James daclan wrote: There are two possible values for "cardinality" (single and |
|
I did this test: I tried to assign a role which cardinality is "single" to more than one person in the team. I saved it and it worked. I didn't see any error.
Is it a right behaviour ? Isn't the rule on cardinality verified ? |
The syntax is in this respect ahead of the actual implementation of our
runtime. The runtime does not enforce the cardinality that is specified. At this point it is a documentation only property. Kai Jazz Process Component Lead daclan wrote: I did this test: I tried to assign a role which cardinality is |
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.