DevOps Center (Managed Package)

After your team manager or Salesforce admin has installed and configured DevOps Center, you’ll be notified that the DevOps Center org is ready for you to log in. As part of the setup process, they created one or more projects, source control project repositories, and work items associated with each project. They also added each team member’s source-tracked development environment.

Note This article provides information about the DevOps Center managed package. Starting in April 2026, Salesforce offers next-generation DevOps Center. For information about the new version, see Next Generation DevOps Center.

• Get Ready to Use a Source Control System
  DevOps Center requires that you use it with a source control system. You can create a new account or use an existing account. Right now, we support GitHub and Bitbucket (beta).
• Open DevOps Center and Select a Project
  Are you ready to begin work? Log in to the DevOps center org, launch DevOps Center, and then select a project.
• Work Item Management
  A team uses work items to track the progress of changes created to achieve a specific objective or task. These tasks can include enabling a user story, creating a feature, or addressing a bug. Managing releases through work items makes it easier to track the progress of the overall release and identify areas of concern.
• What Happens When a Sandbox Is Refreshed
  Refreshing a sandbox creates a new copy of the sandbox based on the production or sandbox org you copy it from.
• Determine Which Changes to Include for the Work Item
  The work item Changes tab is where you can see the changes you made in the development environment. As you make changes in the development environment, the source-tracking feature keeps a record of the component files that have been added, deleted, or changed.
• Commit Changes to the Source Control Repository
  After you decide which changes to include for the work item, commit the changes to the project’s source control repository. When you commit changes, they’re stored in the repository branch that was created when the work item moved to the In Progress stage.
• View Work Item Events in Activity History
  You can view the Activity History for each work item, which provides a comprehensive history of all key events, including promotions, commits, work item status changes, warnings, and errors (failures). This historical view enables you to maintain and view a record of events and associated details for auditing, troubleshooting, and general visibility purposes.
• Synchronize Your Development Environment
  If you’re working on a team with multiple developers, it’s likely that your dev environment is going to become out of sync with the source control repository. DevOps Center tracks the differences between each development environment and the first pipeline stage’s branch.
• Review Changes with Team Members
  When changes for an In Progress work item are committed and ready to share with reviewers, creating a review opens a change request, also called a pull request.
• Indicate That Work Items Are Ready to Promote
  After the work item is reviewed, a team member approves the work item to be ready to promote. Work items aren’t available for promotion through the pipeline until they are in the Ready to Promote status.
• External Change Requests and Merges
  You can create a change request and merge your changes directly in the source control system, which is the first half of the promotion process. You can complete the promotion by deploying all externally merged changes to the pipeline stage’s associated environment within DevOps Center or by using Salesforce CLI.
• Promote Work Items Through Your Pipeline
  You promote work items through a pipeline, which defines the sequence of stages that work items progress as they go through the release lifecycle from development to production (or some other final stage). You can have any number of pipeline stages. Your team manager built the pipeline when configuring DevOps Center.
• View Pipeline Events in Activity History
  DevOps Center provides a comprehensive history of all key pipeline events, including promotions, synchronizations, and errors (failures). You can use these events and their associated details for auditing, troubleshooting, and general visibility purposes.
• Update the Project’s Source API Version Each Salesforce Release
  Because projects in DevOps Center require a source control repository that uses the Salesforce DX project structure, each DevOps Center project contains a configuration file, sfdx-project.json. During each Salesforce release cycle, make a plan to update the source API version to avoid metadata type version mismatch errors when moving changes through your release pipeline.