---
schema_version: "1"
id: a197ed6dca76c56a43f71aa4794a8f86f369bc5249ea0ea73040d46ae5882a99
title: Promote Individual Work Items
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/devops_center_promotion_work_item.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.devops_center_promotion_work_item.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: b567774e19de56817aa8da5ca55c63bcac56a36fc5fa07bc5439647ebb8b7940
description: After a work item is considered “ready to promote,” it’s added to the Approved Work Items list. You can then promote individual work items to the first pipeline stage.
products:
  - Salesforce Platform
release: "264"
---
# Promote Individual Work Items

After a work item is considered “ready to promote,” it’s added to the Approved Work Items list. You can then promote individual work items to the first pipeline stage.

To ensure DevOps Center can process all the changes during the promotion, follow these guidelines to avoid promotion errors.

- Limit the total number of work items to approximately 50 or fewer in each non-bundled pipeline stage.
- When promoting work items from the Approved Work Items list, select up to 15 work items at a time.
- When promoting work items from a non-bundled pipeline stage, up to 25 work items at a time.

1. Click **Pipeline**.
2. Under Approved Work Items, select the work items to promote to the next stage.
3. Click **Promote Selected**.
    
    ![Two work items selected for promotion from Approved Work Items to the Integration stage.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center-264-0-0-production-enus/166010c3-4c34-4087-92ad-aea917baf524/devops_center/images/pipeline-promote-adhoc-approved.png)
4. If you haven’t logged in to the environment for the next pipeline stage from within DevOps Center, complete the login process, then reselect the items to promote and click **Promote Selected**.
5. In the Promotion Options dialog, select a promotion option and which Apex tests to run.
6. Click **Promote**.
    
    If DevOps Center doesn’t detect any conflicts or shared components, the selected work items are merged and deployed to the environment associated with the next stage.
7. (Optional) If DevOps Center detects a dependency or shared components for the selected work items, DevOps Center provides you with the option to combine the work items to address the conflict.
    
    Proceed by choosing one of these options:
    
    - Combine the work items.
        
        For either shared components or a dependency, combine the work items. DevOps Center uses the latest versions of the conflicting components. See [Combine Work Items in DevOps Center (Managed Package)](https://help.salesforce.com/s/articleView?id=platform.devops_center_promotion_combine_work_items.htm&release=264.0.0&type=5 "Prevent potential conflicts during the promotion process by combining work items that share metadata components. In some cases, the source control repository doesn’t know how to reconcile the changes to the same metadata component. Sometimes the promotion is blocked based on a dependency with a shared component. But have no fear, DevOps Center detects the shared components and provides you with a way to promote your changes through the release pipeline with confidence."). Combining work items merges all changes into one feature branch so you avoid downstream merge conflicts.
    - Attempt to promote the originally selected work items.
        
        If shared components are detected, promote the selected work items. However, it’s likely that the other work items, which you don’t choose to promote, still contain conflicts. The promotion is blocked until you manually fix the conflict in the source control system. For GitHub, see [Review and Resolve Conflicts in Your Source Control](https://help.salesforce.com/s/articleView?id=platform.devops_center_promotion_resolve_conflicts_github.htm&release=264.0.0&type=5 "In cases where DevOps Center can’t combine work items or you choose not to combine, DevOps Center blocks the promotion. In this case, you manually edit the files directly in your source control to resolve the conflict in the affected branch."). For Bitbucket, see the Bitbucket documentation.
    - Promote the work item even though there’s a dependency with another work item.
        
        If the promotion is blocked, promote the dependent work item at a later time. However, it’s likely that the other work items still have conflicts. The promotion is blocked until you manually fix the conflict in the source control system. For GitHub, see [Review and Resolve Conflicts in Your Source Control](https://help.salesforce.com/s/articleView?id=platform.devops_center_promotion_resolve_conflicts_github.htm&release=264.0.0&type=5 "In cases where DevOps Center can’t combine work items or you choose not to combine, DevOps Center blocks the promotion. In this case, you manually edit the files directly in your source control to resolve the conflict in the affected branch."). For Bitbucket, see the Bitbucket documentation.

#### See Also

- [Promotion Options](https://help.salesforce.com/s/articleView?id=platform.devops_center_promotion_options.htm&release=264.0.0&type=5 "The available promotion options depend on if you’re promoting individual work items, work item bundles, or performing a validate-only deployment.")