Project level lists
Hi,
How can we define project level lists for work item field values?
I don't want to use local work item lists (for reuse). Allowed values for field in question should differ from project to project. May be we can use some sort of when condition in conjunction with global lists?
Thanks in advance.
Leon
If I understand you question correctly, you want to modify the list of work items that are included by default when you create a Team Project. If this is the case, you need to export your methodology template, modify the template name and the Work Items list, then import the new methodology template.
Is this what you are trying to do?
I believe what Leon wanted was to have lists of field values (not workitems), something like {Dev, Test, Program Management} which could be used to set AllowedValues for a field like "Team". If you did want to change lists of Workitems, then you do need to follow the steps Omar outlined above.
Workitemtracking does not support project scoped lists of strings in v1. You can, ofcourse, create Global lists and have your own naming convention to distinguish between similar lists across multiple projects. eg. Project1_Releases = {M1, M2, RTM} and Project2_Releases = {M1, M2, Beta, RTM}.
You can have project scoped lists of people which you define in GSS and use in your Workitemtypes.
Amit
Hi Amit,
Thanks for your suggestion!
I considered this solution, but how can I select appropriate global list for the field if I want to use the same workitem for different projects?
Hi Ling,
Thanks for your reply, but I don't think this will solve the prolem. Let's say I have two global lists: ProjectA_ItemTypes and ProjectB_ItemTypes to be used as allowed items for ItemType field. If I want to use the same Work Item Type for both projects A and B, how can I define ItemType field?
Thanks,
Leon
Leon, yes, it will not exactly solve your problem. What you want is named lists of strings scoped to Projects, and that is something we do not have for v1.
I hate to suggest it, but one way to work around this would be to write a pre-processor for the WIT which would do something like replace group names with its enumerated children, and do it differently for each project.
Thanks,
Amit
Dev - WorkItemTracking
So basically you suggest to use different WIT for each project to solve it? This means we can not include such a WIT as part of template :) Sad...
Thanks,
Leon
You could also do something like this in your WorkitemType, which you could then reuse across multiple projects. Ofcourse, you will need to add in entries for each new project into the WIT, but you would have had to do something to create new lists for each new project anyway.
<FIELD name="YourField" refname="YourCompany.YourField" type="String">
<WHEN field="System.TeamProject" value="Project1">
<ALLOWEDVALUES>
<LISTITEM value="Proj1_V1"/>
<LISTITEM value="Proj1_V2"/>
</ALLOWEDVALUES>
</WHEN>
<WHEN field="System.TeamProject" value="Project2">
<ALLOWEDVALUES>
<LISTITEM value="Proj2_V1"/>
<LISTITEM value="Proj2_V2"/>
</ALLOWEDVALUES>
</WHEN>
</FIELD>
Thanks,
Amit
Dev-WorkItemTracking
I realize you still cannot use such a WIT as part of a template (the user groups scoped to Projects are meant to support exactly that scenario), but might still be better than processing the WIT by hand every time.
Thanks,
Amit
Dev-WorkItemTracking
Does
System.TeamProject field receive automatically current project name? If it is so, it is good enough solution.
Thanks Amit
Yes, it does. Glad I could help.
Thanks,
Amit
Dev-Workitemtracking