Diagnosing selection problems

Sometimes you need to figure out why a certain object version was or was not selected during an update. Sometimes an occurrence in the build management project hierarchies makes a diagnosis necessary. Other times you might need to help developers with a problem in their development project.

Procedure

  1. Check the process rules for the project to be sure that:
    • The task queries are correct on the folder template.
    • The correct folders or folder templates are a part of the process rule. (You might need to update the process rule if the folders or folder templates for the project are incorrect.)
    • the baseline is set.
  2. Run the update operation, using the verbose option. The verbose option generates extra information about the candidates that are analyzed. It shows the scores for each candidate, and why they received the scores. Troubleshoot using the given information.
    Note: You can perform a verbose update on just the directory with the questionable object version. Limiting the scope is faster than running the verbose update from the top-level project.
  3. Check the project grouping properties.
    • If you turned off Auto Update, be sure that you turned it back on.
    • If you removed a task temporarily, check to be sure that you added it back.
    • If you manually added a task, be sure that you want to keep it.
    • Check that the baseline project is set.
  4. Compare process rules to ensure that they are set correctly.
    1. Right-click over the project or project grouping and choose Process Rule Properties.
    2. In the Process Rule Properties dialog box, click the object menu (located in the upper left corner) and choose Compare with Process Rule from Process.
  5. Right-click over the project you are having problems with and choose Properties. Verify that the baseline project is appropriate.
  6. If you were using a generic process rule that uses the Baseline specified on process rule setting, then added it to a release, specify a baseline for the process rule. If you do not, the project grouping using that process rule does not get a baseline and is not updated correctly. You can specify a baseline in the Process Rules Properties dialog box. (See Modifying the properties of a process rule.)
  7. Compare process rules for two releases. If your projects updated correctly in the last release, but they are not updating properly in your new release, compare the process rules between the two releases. See Comparing two like objects.
  8. Compare the process rule for the current release to the process rule from the process.
  9. Compare update properties for two projects. If two projects for the same purpose and release update differently, compare their update properties. Developer who set their update properties manually can see if the folders in their update properties differ from the folders based on templates. See Changing the update properties for a project.
  10. Compare two folder templates or two folders. Compare folder templates or folders to ensure that your query is correct or to find out which members differ between two folders. See Comparing two like objects.

Feedback