---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Team dashboard

# Team dashboard {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## 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 full answer 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 Team DevelopmentTeam Dashboard.
Figure 1. Team dashboard  
The control panel in the top left provides status indicators and Team Development actions.

* 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](https://servicenow-prod.fluidtopics.net/M4GRiK88nU46q1pJ1~QK_g "If it becomes necessary to modify the instance hierarchy, you can change the parent for a development instance.").
* Reconcile: compares the development instance to the parent instance. See [Reconciling](https://servicenow-prod.fluidtopics.net/4Rwtu23fd0TGj9Af2Id_HA "Reconciling first compares the local instance to the parent, and then generates the list of local changes and calculates the number of changes that are ready to pull from the parent.").
* 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](https://servicenow-prod.fluidtopics.net/diUKUhkwnpFn2Sn5fuSv4A "Pulling retrieves versions of customized records from the parent instance and adds them on the development instance. Pulling does not retrieve any versions for changes made by system upgrades, but it retrieves all versions for changes made by users, not just the current version.").
* Push: opens a page that allows you to review the changes before a push. See [Pushing
  Versions](https://servicenow-prod.fluidtopics.net/mwJGlSYOeysuepco8aeJTg "Pushing promotes changes from the development instance to the parent instance and commits the current version of a customized record on the development instance as the current version on the parent instance.").
* 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](https://servicenow-prod.fluidtopics.net/rHCSjCvfuIgcZLrCC0FLlQ "A collision is detected when the pulled version and the current local version are modifications of a different version, indicating that someone else has modified the same record that you have modified. The team dashboard displays the number of collisions between the local and the parent instance.").
* 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](https://servicenow-prod.fluidtopics.net/rHCSjCvfuIgcZLrCC0FLlQ "A collision is detected when the pulled version and the current local version are modifications of a different version, indicating that someone else has modified the same record that you have modified. The team dashboard displays the number of collisions between the local and the parent instance.").
* Compare to: allows you to select another development instance to compare with the local instance. See [Comparing to
  Peer Instances](https://servicenow-prod.fluidtopics.net/MvYHfPHyCZyXnVXckQLcLg "You can compare the local instance to any other remote instance and commit any current versions from the remote instance on your development instance.").
* Ready to Push: indicates the number of local changes that are queued for the next push. See [Queuing
  and Ignoring Local Changes](https://servicenow-prod.fluidtopics.net/L_BB0eW_e4NsLCLlU6o7~Q "Application developers can queue a local change for a push to ensure the changes are available to other developers.").
* 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.
{#r_TeamDashboard__ul_x5m_vrb_bq}  
The team dashboard includes lists for tracking local changes and viewing the history of Team Development activities.

* 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](https://servicenow-prod.fluidtopics.net/rHCSjCvfuIgcZLrCC0FLlQ "A collision is detected when the pulled version and the current local version are modifications of a different version, indicating that someone else has modified the same record that you have modified. The team dashboard displays the number of collisions between the local and the parent instance.").
* 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.
{#r_TeamDashboard__ul_gf2_tsb_bq}
**Related concepts**   

* [Using Team Development](https://servicenow-prod.fluidtopics.net/rqN4m0ewojYGBrG9jIxuNw "Using team development within your instance to compare instances, push or pull record versions, or view the team development dashboard.")
* [Local changes](https://servicenow-prod.fluidtopics.net/ert2UWc2NtjLW4~bRCZQYA "The Local Changes table tracks which customized records have current versions that exist on the development instance but not on the parent instance.")
* [Local change lists](https://servicenow-prod.fluidtopics.net/2tvWC86sQ380oZwBsFccIg "On the team dashboard, the Local Changes list shows the local changes that have not been queued for the next push or ignored for all pushes.")  
**Related tasks**   

* [Pull a version](https://servicenow-prod.fluidtopics.net/diUKUhkwnpFn2Sn5fuSv4A "Pulling retrieves versions of customized records from the parent instance and adds them on the development instance. Pulling does not retrieve any versions for changes made by system upgrades, but it retrieves all versions for changes made by users, not just the current version.")
* [Resolve a collision in Team Development](https://servicenow-prod.fluidtopics.net/rHCSjCvfuIgcZLrCC0FLlQ "A collision is detected when the pulled version and the current local version are modifications of a different version, indicating that someone else has modified the same record that you have modified. The team dashboard displays the number of collisions between the local and the parent instance.")
* [Resolve multiple collisions](https://servicenow-prod.fluidtopics.net/69of0h9lzO0CXalOHternw "You can resolve multiple collisions without reviewing the differences between the local and pulled versions.")
* [Queue a local change for a push](https://servicenow-prod.fluidtopics.net/L_BB0eW_e4NsLCLlU6o7~Q "Application developers can queue a local change for a push to ensure the changes are available to other developers.")
* [Ignore a local change](https://servicenow-prod.fluidtopics.net/dc9lh0r11kEhIPV8a9qLxA "Ignoring a local change prevents updates to a record from generating new versions in the Local Changes list.")
* [Back out a local change](https://servicenow-prod.fluidtopics.net/ED2biqc0rY9CmIEkBd8Ecg "Back out all local changes and restore the last version reconciled with the parent instance.")
* [Push a version](https://servicenow-prod.fluidtopics.net/mwJGlSYOeysuepco8aeJTg "Pushing promotes changes from the development instance to the parent instance and commits the current version of a customized record on the development instance as the current version on the parent instance.")
* [Approve or reject a push](https://servicenow-prod.fluidtopics.net/mCFymDUskM_AARkyRx8ydQ "Code reviewers must approve or reject a push from the Team Development application.")
* [Check the review status of a pushed change](https://servicenow-prod.fluidtopics.net/m6bXrFYDDg2nqrlNd5SBqg "If the parent instance requires pushed changes to undergo code review, changes are placed in the Awaiting Code Review stage.")
* [Cancel a code review request](https://servicenow-prod.fluidtopics.net/Bnt3yowZdqPoYYQhl_wfSw "Developers can cancel any push they submitted that is in the Awaiting Code Review stage.")
* [Compare to peer instances](https://servicenow-prod.fluidtopics.net/MvYHfPHyCZyXnVXckQLcLg "You can compare the local instance to any other remote instance and commit any current versions from the remote instance on your development instance.")
* [Change the parent instance](https://servicenow-prod.fluidtopics.net/M4GRiK88nU46q1pJ1~QK_g "If it becomes necessary to modify the instance hierarchy, you can change the parent for a development instance.")
* [Reconcile changes](https://servicenow-prod.fluidtopics.net/4Rwtu23fd0TGj9Af2Id_HA "Reconciling first compares the local instance to the parent, and then generates the list of local changes and calculates the number of changes that are ready to pull from the parent.")  
**Related reference**   

* [Pull exceptions](https://servicenow-prod.fluidtopics.net/yKzKNiPXZjzid_UnHYqSUQ "Pulling ignores versions when certain conditions occur.")

*[\>]: and then