MustGather: Agile Planning issues with Engineering Workflow Management

Resolving The Problem

You can use the IBM Support Assistant Data Collector (ISADC) tool to quickly collect diagnostic files, such as log files, configuration files or to run traces. ISADC collects information about your Jazz Team Server environment and stores the information in a .zip archive file. If you have a need to open a service request with IBM Support for further assistance, you can send the archive file with the data collection so that they can help diagnose and fix problems.

The following information should be gathered, in addition to the normal information and log gathering done by ISADC.

General information

Errors in the web UI, which include 'null'2

Firebug trace

Import and export of plans

Performance when working with plans

• Include a screen capture showing the error or bad behavior
   
• Collect the running process template according to How to Extract a Process template from an existing project area
   
• Identify which Roles or Users are incurring the bad behavior
   
• Provide ‘Plan Details’ including 'Options' and 'Column display' view of the problematic plan
   
• Indicate whether the problem occurs with all the plan views or only specific ones. Provide details about the plan view (filters, displayed columns, and more)

• Enable "?debug=true" in the browser and collect a screen capture of the full error
  
  Example: https://<servername>:9443/ccm/web/projects/Project?debug=true#action=com.ibm.team.workitem.viewWorkItem&id=xxx

• If the issue is reproducible in the web UI, add "?debug=true" to the URL and reproduce the issue. Include a screen capture of the ‘console’ section of Firebug for any related errors
   
• Export of the output in the NET tab within Firebug

• In the log4j.properties (..server/ccm/conf), add the following line for trace:
  
  log4j.logger.com.ibm.team.tpt.internal.service.ImpexService=DEBUG
   
• Save the log4j.properties file.
   
• Reload the log4j.properties file by accessing the following link:
  
  https://<server>:9443/ccm/admin?internal=true#action=com.ibm.team.repository.admin.reloadLoggingSettings
  
  (This step avoids having to restart the server)
   
• Reproduce the issue and provide the ccm.log file.

• In the log4j.properties (..server/ccm/conf), add the following line for trace:
  
  log4j.logger.com.ibm.team.apt.internal.service.rest.PlanRestService=TRACE
• Save the log4j.properties file.
   
• Reload the log4j.properties file by accessing the following link:
  
  https://<server>:9443/ccm/admin?internal=true#action=com.ibm.team.repository.admin.reloadLoggingSettings
  
  (This step  avoids having to restart the server)
• Start Developer Tools and navigate to Performance tab.
   
• Click Start Recording Performance button to start recording the session
   
• Reproduce the issue and provide the ccm.log and recorded file.