We were installing the on-premise version of 7pace Timetracker and after finally reaching the point where it begins adding the "Start Tracking" button and the "7pace Timetracker" tab (formerly the "Time" tab) to each work item dialog, an error occurred: "TF237070: Importing the definition failed. The definition you are trying to import did not validate against the schema. Edit the definition, then try to import it again."*
Can you help us to resolve this issue?
*Please note that the error message, above, may or may not contain additional details such as:
- The element 'ALLOWEDVALUES' has incomplete content. List of possible elements expected: 'GLOBALLIST, LISTITEM'.
- The element 'GROUPEDVALUES' has incomplete content. List of possible elements expected: 'GLOBALLIST, LISTITEM'.
Note: This is for on-premise only.
During the installation of 7pace Timetracker, we adjust your work item template by adding 7pace Timetracker-specific elements or contributions such as the "Start Tracking" button and the "7pace Timetracker" tab.
The only way for us to add these extra elements to your work item template is described in the Microsoft article found here. So, unfortunately, there is no way for us to deviate from this process on our side.
DevOps Server behaves inconsistently in that it may work properly with these broken xml definitions day-to-day, however when 7pace Timetracker tries to import them during our installation process, they fail validation and we are unable to add our 7pace Timetracker contributions like "Start Tracking" and the "7pace Timetracker" tab.
The only way to avoid receiving these errors during installation is to fix the broken work item template definitions on your end or to use 7pace Timetracker without its contributions (just click the "Cancel" button on the 7pace Timetracker installation error dialog and you can use it without them).
One example of an issue that could be causing broken work item templates might be:
An error caused by a self-closing tags such as:
<SUGGESTEDVALUES some_parameters />
The valid tag should be:
Please contact Microsoft DevOps Server support; they may be able to provide you with a fix or workaround.