Discovering changes made in your org from a long-running project

Published March 29, 2022
Austin Turner


Let's assume you have been working on a longer running project and your team has been working and building in your sandbox for a few months. You have reached your first milestone in the project and are ready to deploy your MVP to another environment for QA or UAT - but you just realize that the team didn't catalog all the changes along the way and want to make sure that you don't miss anything in your deployment.

Using Jetstream's Deploy Metadata features, you can easily identify and export a list of all the metadata components that were modified during the project.

Selecting Metadata

First, head over to the Deploy Metadata > Compare and Deploy Metadata page. Once here, you will need to choose the types of metadata that you want to compare. While you can select all, you might end up running into issues and waiting a log time for the page to load. It is generally better to target the types of metadata that you think may have changed.

Here are some common metadata types that you might want to choose:


  • ApexClass

  • Apex Trigger

  • Aura Component Bundle

  • Lightning Web Components (LWC)

  • Visualforce Component

  • Visualforce Page

  • StaticResource

Fields and Objects

  • Custom Objects (this includes Custom Settings)

  • Custom Fields

  • Custom Metadata

  • Custom Tabs

  • Compact Layouts

  • Profiles

    • include profiles if you are going to use Jetstream to handle your deployment and want to include FLS

  • Page Layouts

  • Lightning Record Pages

  • List Views

  • Permission Sets

  • Quick Actions

  • Validation Rules

  • Web Link (aka page buttons for classic)


  • Flow (this includes Process Builders)

  • Workflow Rule

  • Workflow Alert

  • Workflow Field Update

  • Workflow Send

  • Workflow Task

This list may not include everything you may want to select, but should give you a good starting point.

Adding filters

If you want to add some filters to start off with, you can, but since we have a large project with multiple developers and admins, we are going to show all metadata and will filter after the fact.

Working with the list of Metadata

Once all of your metadata has fully loaded, you can easily work with the table to find and identify the items that your team has made changes to in your sandbox.

Working with metadata types

You can collapse the various metadata types or filter against the metadata column to change which types you want to look at.


Filtering by last modified person

Using the column filters for Last Modified By and Last Modified, you can quickly identify all the components that were modified by certain people after a specific date range. Usually you will want to use the Greater Than date filter, but you can also configure a time-period range.


Beware of gotcha's

Some metadata types do not have accurate Created and Last Modified dates, such as standard objects and fields or Custom Metadata.


Exporting data

Once you have selected all the metadata that was modified as part of your project, you have a few options from here.

  • You can export a spreadsheet of all of your selected items - this makes a great starting point for a configuration log

  • You can deploy the metadata to another org

  • You can add the metadata to an outbound changeset

    • ⚠ Be aware that doing so will update the modified by person and last modified date, since this requires re-deploying the items to your org

  • ⭐ Compare the metadata with another org to look at the exact changes made to each item

    • Click the "View or Compare Selected Items" button to start this process

  • You can download all the metadata as a zip file, which you can deploy to another org or save as a backup


And that's it! In just a few minutes you have a grasp of all the metadata that was modified as part of your project!

If you haven't yet checked out Jetstream, take a look and see what you are missing!