dropdown shows all valid users for the field
shows work item assigned to value for each work item (same as IDE) Refresh in project: one of work items now has aDeveloper set to valid value Field values: all empty (because we haven’t populated this field in work item tracking for any workĭisplay the ‘aDeveloper’ field, and set the value to a valid value from the dropdown all valid users for the field, not merely those corresponding to exported work items Assigned To them In the pasted xml, set name=”aDeveloper” refname=”Common.aDeveloper” // where "aDeveloper" is a field name you have not used before Same behavior when click on Resource Name cell for work item as lower in column (empty row)Ĭopy field definition ‘Assigned To’ in Task.xml:Īnd paste the snippet just below the original. all valid users for the field, not merely those corresponding toĢ. Can key valid users that do not appearĮxport query ‘a’ of work items to MS Project, where some, but not all, of the valid users (for the field) have work items assigned to themġ. Same behavior when click on Resource Name cell for work item as lower in column (empty row)Ĭ. See only users to whom exported work items are assigned Assigned to exported to Resource names: ok
My suggestion is to simplify your scenario and see if you can get that working first. I've pasted below a simplified version and called out the expected behavior differences for 'Assigned To' mapped to pjTaskResourceNames (the default),ġ) Out-of-box (OOB) Agile Process Template, OOB ‘Task’ work item type and and OOB TfsFieldMappingĮxport work items to MS Project, where some, but not all, of the valid users (for the field) have work items assigned to themĪ.
0 kommentar(er)
