Help us improve Gearset
We love getting feedback from our users on how we can make Gearset even better. Post your ideas for improvements, new features, and bug fixes alike, and vote for others – let us know what’s important to you.
165 results found
-
On Create Pull Request, auto populate details with commit messages
Similar to the way Bitbucket and GitHub work, it would be nice if the PR description was autopopulated from the commit messages (1 per line)
3 votes -
Include Deployment Name on Continuous integration dashboard
On the Continuous integration dashboard, specifically in the Validation only CI jobs section, there is no way to associate a validation job with the deployment dashboard in Salesforce. We have a validation only job set up to run tests on PRs when they're created. If we get a handful of them all at once, there is a long list of validation jobs running, but we can't tell which one is the one that's actively running. There is no link between the job in gearset and the job in salesforce.
3 votes -
Empty cache during meta deployment process
Before you deploy but after you start the process it should be possible to refresh / empty cache to make sure that any updates to the meta data in either source or target are updated.
3 votes -
Gearset should control the order of deployment for Report Types, Reports and Dashboards
Dashboards require Reports, and Reports require Report Types. Yet when I attempt to deploy a group of components that comprises all of the necessary components, I'm hit with errors that the required components don't exist <yet>. That shouldn't happen. This is going to <artificially> require me to do multiple deployments. :(
3 votes -
Control When Tests are Ran Based on Metadata type
It would be nice to control when we want tests to run based on the type of changes in the triggering event for CI. Something like only run test classes on update of Apex Classes, Flows, Workflows, and Objects.
This is a bit of a patch for not having test classes fully optimized but would be helpful with orgs who have lots of profile and layout changes.3 votes -
Add an option to not run the comparision part in CI job (sfdx like)
When you are pushing a project with sfdx, there is no compare, sfdx just push the whole package.
It will save a lot of times.
3 votes -
Find/Replace before deployment
Allow a basic find/replace to run against files before final deployment.
Examples: a username that would work in the sandbox that does not exist in production and we need to change it. Or deploying to a packaging org required a modification due to various namespace issues. Other tools have a means to do this in one way or another.3 votes -
Deploy SOAP APIs like Permissionset assignment
I am able to deploy profile components and permission sets separately. But the permission set assignment is part of salesforce SOAP API and I couldn't deploy the same using GearSet.
Kindly provide deployment options not only for Metadata API, also SOAP APIs3 votes -
3 votes
-
Pipeline Sync Environment & Dev Environment
Currently we only have the ability to sync static pipeline environments. This is well and good but unfortunately syncing the Project branch can be time consuming and confusing Its not as simple as syncing the static environment.
I suggest when I sync the static environment , the sync action automatically opens a back propagation PR to the Dev environment its connected to. Also this sync action should close any pending open PRs against that dev environment that overlap with the sync PR.
2 votes -
Remove limitation of number of PRs to be added to a Release (Azure DevOps + Gearset)
Gearset automatically adds all PR details for a release in description box (Azure DevOps PR) which has max character limit of 4000 and only 16-18 PRs can be added to a release because of it. When we add one more PR after the limit is reached then the next PR does not get added to the Release and we need to create another release for them which is not correct approach as other releases may have some dependency on 1st and thing may fail in production. We need a way to disable adding description to Azure DevOps Release PR so…
2 votes -
Granular Permissions
Most of our users don't need to be doing any configuration outside of connecting their Dev Sandbox. Prefer to have more granular permissions to lock down features to smaller groups of users.
2 votes -
Run pull request validation against a different sandbox than the one linked to the target org
Hi team,
We have multiple developers creating PRs against a common development branch (let's call it simple, develop; developers are creating their feature branches from master, the Production configuration branch). Develop branch is linked to an integration environment (called INT). INT environment contains multiple stories which are not yet in Production (some of them might go in Production, some will not go).
I would like to get my PRs validated in a Production-copy environment (called BUILDCHK) just to get a real feedback on how "deployable" are my changes in Production, for whenever their time will come.
It would be great…
2 votes -
Feature vs Release, Branch De-sync
When Gearset detects that additional changes have been made to a feature branch AFTER the feature branch was already added to a Release, strange behavior may be experienced.
Coming from a git background, I expected anything on the release branch would be ready to go on my deployment, but that is not what happened during my release window.
Admittedly there were some features that had changes pushed to the feature branch after perhaps the feature branch should have been closed, namely after it was on the Release branch. However there's also an argument that we should trust whats on the…
2 votes -
"Sync environment" automation
On the pipeline, the action of "Sync environment" is currently a manual action. It could be useful to have an automation of this action (like the back-propagation) after each Production Deployment. This step is a little bit time consuming and can be easily missed. If we had an automatic creation of this synchronization PR on each CI Job it would make the processus more fluid.
2 votes -
Allow Quick Deploy when merging multiple PRs using Pipelines
currently when merging multiple prs using pipelines the merged package validates and then the prs are merged, the resulting deployment then revalidates even though quick deploy is an option, can we use quick deploy when available like was enabled in the ci jobs?
this would save time by avoiding double validation and make the feature more usefull.
2 votes -
Schedule deployment option for validation only CI jobs
It could be good that time selection schedule option is available, makes release timetable easier to execute to target org.
Currently user can only execute the pre validated package immediately.
2 votes -
Revert with one click all changes from this PR
Please allow reverting PR from lower environments. In mine example, we had a feature that went through develop and uat and was waiting in the pipeline to be added to release but the business changed its mind and canceled this whole feature.
Please add an option that with one click we can revert PR and changes from lower environments.
Image:
https://www.dropbox.com/s/ohvymcs16p9n5ge/2022-06-30_14h10_44.png?dl=02 votes -
to let us configure the default metadata filter by deployment pipeline configuration
Can we please have a possibility to configure the "standard" metadata filter by each deployment pipeline project?
I think it is currently preselected by the last used metadata filter from the standard comparison.
As we usually have a specific metadata filter configured by deployment pipeline project, it would be great that we can configure each project with a default one..
Thank you!
2 votes -
Possibility to validate a feature branch as a whole without having to select the Metadata type
It looks like the current validation jobs setup in Gearset needs the Metadata Type to be explicitly selected to perform the validation. This should ideally be optional and there should be a capability to just validate everything that is there in the feature branch against the target org. It's really annoying for us that we have to select the Metadata Types to be validated.
2 votes
- Don't see your idea?