Loading
Salesforce now sends email only from verified domains. Read More
Manage and Release Changes Easily and Collaboratively with DevOps...
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Manage the Work Item Lifecycle with DevOps Center MCP Tools

            You are here:

            1. Salesforce Help
            2. Docs
            3. DevOps Center

            Manage the Work Item Lifecycle with DevOps Center MCP Tools

            Use the next-generation DevOps Center MCP tools to manage your work item’s lifecycle end-to-end. You can handle work item creation, user assignments, code changes, pull requests, and promotions directly through natural language prompts.

            Required Editions

            Available in: Lightning Experience in Professional (API access required), Enterprise, Performance, Unlimited, and Developer Editions
            Available in: Government Cloud Plus as interoperable. Turning on DevOps Center in Government Cloud Plus orgs can send data outside the authorization boundary. Contact your Salesforce account executive for more details.
            Not available in: EU Operating Zone. EU Operating zone is a special paid offering that provides an enhanced level of data residency commitment. DevOps Center is supported in orgs in the EU that aren’t part of EU OZ, per standard product terms and conditions.

            Before you begin, set up the Salesforce DX MCP Server. See Access the DevOps Center MCP Tools.

            Step 1: Start with a work item

            Identify your assigned tasks and prepare your local environment for development.

            Prompt
            “Show all open work items assigned to me. ”
            How It Works
            The list_devops_center_work_items tool returns a list of work items, including their titles, branches, environments, and statuses.
            Sample Response 
            “Ok. Here are your open work items:
            Work Item: WI-001234
            Title: Bug Fix for Account Creation
            Branch:bugfix/account-create
            Environment: UAT
            Status: In Progress"
            Prompt
            “Let’s start working on WI-001234.”
            How It Works
            The update_devops_center_work_item_status tool updates the work item status to In Progress. Then the checkout_devops_center_work_item tool checks out the specified work item and prepares your local environment.
            Sample Response 
            “Ok. WI-001234 is In Progress. Checking out Work Item WI-1234 and preparing your development environment."

            Step 2: Commit changes

            After making your code changes, commit them to the source control repository.

            Prompt
            “Commit changes: Fixed validation for Contact email.”
            How It Works
            The commit_devops_center_work_item tool verifies the current Git branch, adds the work item ID to the commit metadata, and commits the changes.
            Sample Response 
            “Acknowledged. Committing changes with the message 'Fixed validation for Contact email'. The work item ID is added to the commit metadata."

            Step 3: Create a pull request

            Once your changes are committed, initiate the review process.

            Prompt
            “Create a review for WI-001234.”
            How It Works
            The create_devops_center_pull_request tool first checks if your commits are pushed to the remote repository.
            • If commits aren’t pushed, the tool blocks the action and prompts you to push them.
            • If commits are pushed, the tool creates a pull request and returns the ID and URL.
            Sample Response 
            “Understood. Creating a pull request. Once complete, I will provide the Pull Request ID and URL.
            Here’s the final output:
            Pull Request ID: PR-102
            Pull Request URL: https://your-devops-platform.com/project-alpha/pull-requests/5678"

            Step 4: Review and approve pull requests

            Open the URL provided in the previous step to review and approve the pull request directly in your source control.

            Step 5: Mark the work item as Ready to Promote

            After the pull request is approved, mark the work item as Ready to Promote to notify the deployment manager that the work item is ready for the next step.

            Prompt
            “Mark WI-001234 as ready to promote.”
            How It Works
            The update_devops_center_work_item_status tool updates the work item status to Ready to Promote.
            Sample Response 
            “The work item WI-1234 is In Progress, so I’ll mark it Ready to Promote."

            Step 6: Promote the work item

            After the pull request is approved, deploy the changes to the next environment.

            Prompt
            “Promote WI-1234 to UAT.”
            How It Works
            The promote_devops_center_work_item tool identifies the work item ID and target environment, merges the feature branch, and deploys the metadata.
            Sample Response 
            “Promotion of WI-001234 to UAT is initiated. You can monitor the progress and view logs in DevOps Center."
             
            Loading
            Salesforce Help | Article