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.
1139 results found
-
Allow squash merge for Github PR
We have our GitHub PR settings set to only allow Squash and Merge for PRs because we want a clean history on the long-lived branches. It seems Gearset doesn't support this, when I attempt to promote it issues an error. This should be configurable or should detect this automatically from the settings.
2 votes -
Validation job when PRs are raised
Requirement :
Provide option to create a CI Validation Job only with "Validate pull requests targeting the source branch" and keep "Run Job" dropdown as optional .As Of Now :
When we raise a PR, it initiates feature branch validation ( cos, we enabled "Validate pull requests targeting the source branch" ), and after that when we merge feature-branch to target branch, it re-initiates another validation job.
For us, it's like similar validation is running twice on different events from which we can't opt out.Pros :
We can handle when to validate a feature branch, instead of bundling…
1 vote -
Consolidated Reporting for CI Jobs
Hello. One item we struggle with is keeping track of CI Deployments that didn't fail, but didn't deploy as expected. The two causes we usually see are:
1) Something was removed by problem analyzer
2) We deployed something that Salesforce says succeeded, but no changes were made (e.g. deletion of picklist choices)We currently have about 100 CI jobs which makes it impractical to go into each one.
The proposed format would look like a csv export:
Job Name, Date, # Created, # Updated, # Deleted, # fixed by problem analyzer
Opening a CI job history looks fine, but we'd…
1 vote -
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 -
Have the Jira ticket which was selected at the point of the commit stay with the PR in Pipelines
At the moment when you select a Jira ticket at the point of commiting to a branch, you are able to track that actionback into Jira.
However when a PR is opened from that feature branch to the next environment branch (in the Pipelines UI specifically) the Jira ticket association is lost, and has to be reattached manually.
Workarounds:
1. Manually add the ticket ID to the PR description, which will reassociate it
2. Use the drop down menu provided in the Pipelines UI to re select the Jira ticket
3. Open the PR from the Commit successful screen…2 votes -
Make "Hide Reodering" global switch
Please add a feature to have globally selected "Hide Reordering" and also hide those files that have no changes after reordering from Changed Items?
Clicking that on every file to see that there are no real differences is time consuming and slow down the comparison process.
Scenario:
1. I am comparing two sandboxes develop with my private sandbox to align with changes made on develop.
2. I have comparison with many Global Value Sets, Custom fields which are Picklists, flows etc.
3. Most of them are not changed but are listed as changes. I need to click on each metadata…12 votes -
Make it available to commit custom labels that are part of a managed package
Custom Labels of managed packages do not show up in the comparison because they cannot be changed and therefore are not deployable. However, the (override) translations of these Custom Labels do show up and are deployable. It is possible to deploy & commit the translations but this poses an issue if you commit to git since gearset suggests to leave them out of the commit because they are missing a dependency. If you ignore the suggestion and commit them anyway, they'll be removed the next time the repo cleaner runs. This way, it cannot reliably be kept in git.
2 votes -
Disable Jira notifications for individual CI Jobs
We like that the Jira integration posts changes to the associated Jira ticket during a deployment, but we only want notifications for specific CI Jobs. For example we want our staging and prod deployments to post a notification in our Jira ticket, but not for other jobs such as back-deployments. Each post potentially emails Jira users and we want to limit these notifications. Currently the only work around is to remove the Jira ticket association from the PR in Gearset before promoting it, and this gets tedious if you have a lot of development orgs.
2 votes -
Include Apex classes regardless of folder
In GitHub, Apex classes don't always have to be in a folder called "classes " to work with them. Some people using SFDX put test classes in their own folder (sometimes called "tests". Even Apex classes within the "classes" folder can be sub-grouped into folders. (Example at https://github.com/trailheadapps/apex-recipes/tree/main/force-app/main/default/classes)
I'd like Gearset to scan the entire repository and to group metadata by its actual type, not by the folder it is in.
I'm not talking about the sfdx-project.json saying where the metadata is located. This is within each of those locations, it should find all Apex (for example). The Apex…1 vote -
Provide More Detailed Information on Data Deployment Summary Steps
Currently the data deployment summary displays an elaborate interface but with very little useful information other than record counts. On the right side are Steps, but those steps do not tell the user much. I can see that in one step x records were fetched, for example, and in another step y records were fetched, but I can't see WHY.
Example use case: I had a situation where I was filtering an object but the filter wasn't being honored (more records were being deployed than expected). I could see from the data deployment summary that one of the steps was…
1 vote -
Pipeline automatic back promote
When using pipelines, it would be helpful to have the option to automatically back promote changes through the pipeline. For example, we currently have a CI job that pushes specific changes that admins are allowed to make directly in production into our master branch. We then have a Github Action that automatically merges commits to our master branch to the other branches in the pipeline, so that everything is synced. However, in order to turn on pipeline, we have to turn off our automated merge action, because pipeline creates a bunch of PRs when the automation runs. This forces someone…
5 votes -
Customize CI job commit message
When a CI job pushes changes to source control, it always uses the message "CI deployment from job <CI job name>". It would be very helpful to be able to customize this message.
5 votes -
Add a way so we can easily integrate commits into Salesforce.
What I mean by this is, give users the ability to create and associate commits from in Gearset to a custom Object in Salesforce.
The commit would create a new record in Salesforce, under the custom object, let's call it 'Commits'.
We'd be able to pass through data such as the commit status, the ID of the commit, a link to the commit itself taking us back to Gearset, the name, and author, etc, etc...
I'd imagine this is possible through the use of the BitBucket API, however with SF teams who lack developer resources, this would be a nice…
1 vote -
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 -
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 -
Notify GitHub that checks are running sooner
When a PR in GitHub is being validated, Gearset doesn't let GitHub know that the check is happening until after it has run the comparison between GitHub and the target org. Then the check is pending while the validation runs in Salesforce.
This means that there is a delay between when you create a PR and Gearset's check appearing as pending in the PR. At that moment, it looks like there are no more checks to run in GitHub so you can go ahead and merge. But, you really should wait until Gearset has compared and validated the changes.
It…
2 votes -
Delete GitHub webhook when the CI job is deleted
When we create a CI job where the source is GitHub, Gearset can automatically create a webhook for us in GitHub.
Would it be possible to delete that webhook in GitHub when we delete the CI job from Gearset? I've got some GitHub repos with failing webhooks due to CI jobs I once created. Obviously, I can tidy up manually from GitHub, but it would be nice to have the option of Gearset doing it for me. The URL seems to be unique to the CI job, so I can't see it having any negative consequences.
3 votes -
Allow for Object Deployments without subcomponents to git
When deploying an object to git currently there is no support to ONLY deploy the object metadata.
We have a large managed package that your code requires the .object file for an object in that managed package to exist for me to deploy fields or other customizations for said object git -> org. When I deploy org -> git to get the .object file into my repo it also grabs all the fields on the managed package object which I don't want/need.
I don't want the fields and I need to specifically get it from the target org because if…4 votes -
Make Pipelines a Top-Level Menu Item
This is a less-good, but arguably easier to implement, version of my request for customizable landing pages. It takes a few clicks to get to pipelines and, since it's the place I live most often inside of Gearset these days, I'd love it if it was a menu option that is parallel to "Continuous Integration" so I could get there in fewer clicks.
4 votes -
Enable source control as source/target in Data Deployments
It would be great if we could add source control as an option for Data Deployments, this will be useful in cases where we want to backup copies of CPQ record data which manage configurations to our source control repository.
3 votes
- Don't see your idea?