When linking a child WIT to a parent in TFS I'd like to copy values from the parent into a child WIT Template. If the parent WIT has a title of xyz and I'm linking a child WIT and creating a new template for it, I want to grab the parent values from certain fields, mainly title. I think people deciphered my original request but hopefully this is a little cleaner.
No, it's not supported.
Copy rule only available within the work item itself:
You can use the COPY, DEFAULT, and SERVERDEFAULT elements to
copy a value from one field to another, copy a server value into a
field, or specify a default value to be defined for a field.
Source here: Define a default value or copy a value to a field
Parent/Child just links between work items, but no any relationship eachother accross the value of the fileds.
Related
We have site where a user went to the Data Types, saw we had a Content Picker data type using "(Obsolete) Content Picker" (Umbraco.ContentPickerAlias) and changed it to Umbraco.ContentPicker2
Our code relies on the obsolete one currently and now he cannot set the content we want him to.
Is there a way to recreate/reimport the Obsolete property editor into Umbraco?
On the Data Types node you can click on the ... and create a 'New data type' - then select the obsolete one to create it again.
But in theory, I believe you could just do the opposite of what the user did, on the ContentPicker click edit and pick the property editor from the dropdown if available?
Within the umbracoSettings.config file, there is a property you can create/set to true that will make obsolete data types become available to use against data types
<showDeprecatedPropertyEditors>true</showDeprecatedPropertyEditors>
how to implement a state change in TFS 2012, when any fields are changed in that work item type.
I have a task work item type which is set to "proposed". When the field/fields are changed in task work item, state should be changed to "Active" automatically.
You need to customize the work item definition and add a rule to the field. Refer to this link for details: Working with Field Rules and Assign Conditional-Based Values and Rules
Depending on the data type of a field, you can set various
restrictions on what data can be entered into that field. For example,
you can define a default value, restrict what values users can
specify, and restrict who can update the value of the field. You may
want to apply a rule to a work item field for one or more of the
following reasons:
Specify the tooltip text that appears when a user hovers over a field in a work item form.
Require the value of a string field to match a pattern.
Make a field required or read-only, or make sure that it does not contain the same value as another field.
Clear a field, or restrict further modifications of a field.
Restrict who can modify the field.
Apply a rule to a field when the value of another field has changed or is assigned a specific value.
Update:
For System fields, there is some restriction for them. Refer to this link for details: Q: What rules can be applied to System fields?
Q: What rules can be applied to System fields? A: System fields have
Sytem.Name reference names, for example System.Title and System.State.
TFS restricts customization of these fields, except for these
instances: HELPTEXT rule can be assigned to all fields. READONLY rule
can be assigned to the State and Reason fields. Most rules can be
assigned to the Title, Assigned To, Description or Changed By System
fields.
That means, you cannot apply the rule to change the state in your case.
I think the answer is no, but the question has been put to me so I'd like to confirm. My understanding is that any custom XBL control that I create for use in Form Builder can have one and only one value. Is this correct?
I have always assumed this because the control name is then used in the data instance as the name of the node which contains the the value.
This question comes from the desire to have reusable components with multiple values, for example, an Address control so that addresses can be recorded consistently and the same set of fields does not need to be added many times. Orbeon does have some support for this in the form of Section Templates but because the control names stay the same in each instance of a Section Template this does not work well with our design.
The best idea I've had is that a custom control which records multiple values could encode all the values into a single text string for example in JSON. Of course, this is not ideal.
Are there any other options?
It is possible for controls to have multiple values. When that happens the values are typically stored in nested elements. I.e. a control could bound to an element <address>, and could create nested elements <street>, <city>,<country>, etc to store the different parts of the address.
In practice, you can look at how this is done in the Image Annotation annotation control (see wpaint.xbl), which creates nested elements <image> and <annotation>, leveraging the xxbl:mirror="true" functionality.
We want to extend the bug work item template with a new field called Found In Iteration. This field, what a surprise, should contains the iteration the bug was found in. But when I created the new field of type TreePath, I got an error when importing the process template into the Team Project Collection (TPC) stating that TreePath is only a valid field type for IterationPath and AreaPath fields.
Looking at that I'm wondering if there is at least any way to add a field to a work item template that uses the iteration path as data source and stores the selected value in another field (e.g. FoundInIteration).
This is not possible. There can neither be custom fields of type TreePath nor fields refering to System.IterationPath.
We have a TFS team project using the Agile process template.
We have added a string field to the User Story and Task work item types.
This field is a dropdown bound to a global list.
When you create a new linked workitem from an existing workitem (using the NEW button on the LINKS tab for example), the Assigned To, Area and Iteration values are copied to the new linked item.
We would like to also copy the value for the string field that we've added, so that it does not have to be set manually.
Any ideas if this is possible using TFS customization?
It's possible... but not with "out of the box" work item features. You'd need to write some custom code with the SDK (http://archive.msdn.microsoft.com/tfssdk) to get this behavior.