Team dashboard
Summarize
Summary of Team dashboard
The Team dashboard in ServiceNow's Yokohama release centralizes all Team Development activities on your development instance. It enables you to manage and track local changes, synchronize changes with a parent instance, compare your instance with other development instances, and resolve conflicts or collisions that arise during development.
Show less
Access the dashboard by navigating to Team Development > Team Dashboard.
Key Features
- Control Panel Status Indicators: Displays the connection status to the parent instance, local change status, collision alerts, and readiness for pull or push actions.
- Parent Instance Management: View connection status, change the parent instance, and reconcile differences between your instance and the current parent.
- Change Synchronization: Pull changes from the parent instance, push local changes to the parent, and queue or ignore local changes before pushing.
- Collision Detection and Resolution: Identifies local changes that conflict with pulled changes. Collisions must be resolved before pulling or pushing further changes.
- Instance Comparison: Select and compare your local instance with other development instances to track differences and changes.
- Change Tracking Lists: Includes lists for local changes (queued, ignored, and unqueued), history of pushes and pulls, instance comparisons, and collisions.
Practical Use and Benefits
ServiceNow customers can use the Team dashboard to maintain synchronization across multiple development instances, ensuring smooth collaboration and minimizing integration conflicts. The dashboard’s indicators and lists provide clear visibility into the status of changes, helping teams to manage code versions effectively and resolve conflicts promptly.
By leveraging the dashboard’s features, teams can:
- Track and manage local development changes efficiently.
- Synchronize changes reliably with the parent and peer instances.
- Identify and resolve collisions early to prevent deployment issues.
- Maintain an organized history of development activities for audit and review purposes.
Next Steps
To fully utilize the Team dashboard, customers should familiarize themselves with related tasks such as pulling and pushing versions, resolving collisions, queuing or ignoring changes, changing the parent instance, and reconciling differences. These tasks ensure effective version control and collaboration within the ServiceNow development environment.
The team dashboard provides a central place to manage all Team Development activities on your development instance.
You can track local changes, pull and push changes between the local and parent instances, compare the local instance to other development instances, and resolve any collisions. You can also reconcile with the current parent instance or change the parent instance.
To access the dashboard, navigate to .
- Parent: indicates the status of the connection to the parent instance. If a problem or warning is detected, point to the indicator to view the error messages, or click the indicator to open the remote instance record.
- Change: changes the parent instance. See Changing the Parent Instance.
- Reconcile: compares the development instance to the parent instance. See Reconciling.
- Ready to Pull: indicates the number of changes on the parent that have not been pulled to the local instance.
- Pull: initiates a pull. See Pulling Versions.
- Push: opens a page that allows you to review the changes before a push. See Pushing Versions.
- Refresh: updates the status indicators on the control panel. The dashboard updates only when you reload or refresh the page.
- Local: indicates the status of the most recent comparison with another instance. If collisions are detected, click the indicator to open the list and resolve the collisions. See Resolve a collision in Team Development.
- Collisions: appears only if any local changes collide with versions pulled from the parent and indicates the number of collisions. Click the indicator to open the list and resolve the collisions. See Resolve a collision in Team Development.
- Compare to: allows you to select another development instance to compare with the local instance. See Comparing to Peer Instances.
- Ready to Push: indicates the number of local changes that are queued for the next push. See Queuing and Ignoring Local Changes.
- Local changes: indicates the number of local changes that have not been queued or ignored. Click the indicator to open a list of these changes.
- Ignored: appears only if any local changes are ignored and indicates the number of ignored changes. Click the indicator to open a list of these changes.
- Local changes: lists the local changes that have not been queued or ignored.
- Pushes and Pulls: provides a history of pushes and pulls. Expand a row to see the customized records for which versions were transferred as part of the push or pull.
- Instance Comparisons: provides a history of comparisons with other development instances.
- Collisions: lists the collisions that must be resolved before the next pull or push. You can right-click a row and select Resolve Collision. See Resolving Collisions.
- Ready to Push: lists the local changes that have been queued for the next push.
- Ignored: lists the local changes that are ignored for all pushes.