forcedotcom / forcedotcom/devops-center-feedback
Feedback on Setup
- 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.**
General feedback on the setup process first impressions
**Describe the solution you'd like**
Liked the new environment setup and being led through the missing setup actions. Would like to see the following though in the GA release:
1. When I added my production environment it wasn't automatically added as production in my pipeline. Although I can see some clients may be deploying to multiple production orgs, they should really use packaging for those scenarios.
2. When prompted to add my first sandbox environment I didn't notice the checkbox to indicate it was a dev org, I'd need to repeat the exercise from scratch to check if that was missing or my error. Easily rectified by removing and re-adding the org.
3. I like the bundling stage radio button to select the org changes becomes a release artifact
4. Navigating between Pipeline and Settings would be unnecessary if there was a Add New option in the Environment pick list on the Pipeline page
5. If I gave an environment the wrong name I had to remove and re-add it. I don't expect this to be a big issue and I'll see what issues removing an environment, re-adding it and re-associating it with the original branch causes.
6. Documentation is very thorough, but ultimately the app is easy to use and I found myself just getting on with it and only going back to the notes to see if I'd missed anything.
7. One time saver is around Access Control. If adding users was centralised and provisioned both access to the Git repo and a developer license to the DevHub org that could be helpful. Noted its a one time issue and not a huge burden.
**Additional context**
Add any other context or screenshots about the feature request here.
Contributor guide
Assessment
This issue has not been assessed yet.