forcedotcom / forcedotcom/devops-center-roadmap
Feature Request: Granular Component Deployment in Salesforce DevOps Center
- Dominant language
- No language data
- Stars
- 27
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Current Situation
In Salesforce DevOps Center, when components are modified in a sandbox environment, all changes to a component are grouped together in a work item. When pushing changes to subsequent environments, all modifications to a component must be moved together.
Problem
This approach lacks granularity and can lead to unintended deployments. For example:
If an admin creates two new custom objects in a sandbox:
FavoriteIceCream__c
FavoriteColor__c
To deploy only FavoriteIceCream__c, the admin must also deploy FavoriteColor__c because the Admin profile touches both objects.
Similarly, release updates installed in the development environment must be moved to production, even if not intended for immediate application.
Proposed Solution
Implement granular selection of component attributes for deployment:
Break down components into individual attributes in the work item's list of changes.
Allow users to select specific attributes of a component for deployment.
For profile changes, create separate attributes for each affected object or component.
Example
Instead of grouping all Admin profile changes together:
Create two separate 'Admin' attributes in the change list:
Admin: FavoriteIceCream__c
Admin: FavoriteColor__c
Users can then select only the relevant attribute(s) for deployment.
Benefits
Increased control over deployments
Ability to work on multiple projects simultaneously without interference
Prevention of premature release update deployments
Improved isolation of project components
This enhancement would significantly improve the flexibility and precision of the Salesforce DevOps Center, allowing for more efficient and controlled development processes.
Contributor guide
Assessment
This issue has not been assessed yet.