forcedotcom / forcedotcom/devops-center-feedback

Being able to setup environments for different projects

Open
#96 2 comments 4 reactions 0 assignees View on GitHub
Env management USER STORY
Dominant language
No language data
Stars
61
Forks
2
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

**Describe the solution you'd like**
For each “DevOps Center” project, you have to specify/setup the different environments. It should be great to be able to use the same environments for different projects. It makes no sense to do this for every project (unless the pipeline is different for different projects).
In the real life, big customers manage Salesforce projects using a release strategy. In many cases and for each release, they are using the same environments/environment strategy.

Contributor guide

Open the contributing guide

Research direction

The issue describes reusing one environment strategy across multiple DevOps Center projects, especially for Salesforce release workflows. No files, tests, or implementation entry points are named; first clarify how projects and environments are currently configured, then define the supported reuse behavior and its completion criteria.

Written by the indexing model from the issue text.

Assessment

Domain
devops, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.