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.
1304 results found
-
1 vote
-
When Deploying A Page Layout, Consider Quick Actions to be Dependencies When Checking for Package Issues
Problem analysis doesn't catch if a page layout has a Quick Action that isn't present in the destination. This causes the package to error on send.
1 vote -
Read the PR title and prevent making feature branches for specific PRs against pipeline branches
If Dependabot opens a PR to update, say, a dev-dependency, then Gearset intercepts that and does its thing, including back-propagating that PR. But if I'm making branches from main, all I need is that PR to be merged to main, and it will come along the pipeline with other PRs opened against the beginning of my pipeline.
If you read [skip ci] in the PR title, or perhaps if the PR starts with a specific prefix (like ci or build, which would follow conventional commits) then just let that PR go against main and ignore it.
I have workflow to…
1 vote -
Allow a PR template from GitHub to pre-populate the PR description
There is a feature in GitHub to auto-populate the PR description (forcing, for example, a checklist if using the web UI). If Gearset could read that template and pre-populate the PR description so users have to put in specific comments (such as manual steps to be done after deployment) and if that description were exposed in GitHub, then it would be more seamless and the deployment history would enable an admin to work through each manual step without looking in closed PRs in Gearset.
2 votes -
Don't include Wave dataflow deletes in package when Recipe is included
When deploying deletes of Wave recipes, if you include the Dataflow at the same time, Salesforce will fail validation with a DataFlow not found error. GearSet should be smart enough to build the package without the Dataflow if the corresponding Recipe is marked for delete.
1 vote -
Create ListViews in the Continuous Integration Dashboard
Create ListViews in the Continuous Integration Dashboard page and being able to grant access to specific users or groups of users.
The idea is to avoid displaying specific jobs to a particular group of users for better organization and reduce the loading time when many CI jobs are configured.
3 votes -
ClickUp integration would be awesome!
My company uses ClickUp to manage tickets, would be great if there was integration with Gearset as that would save me copy/pasting ticket references into the deployment descriptions.
4 votes -
Schedule Delta CI Job to Run at Specific Time
I would like the ability to schedule a Delta CI Deployment Job at a specific time. We have a requirement to deploy at weird times every once in a while.
Code gets merged into our MAIN branch > Delta CI Deployment Job is disabled > click "run" on the job at specific time.
It would be great if someone didn't have to wake up at 3am to click the "run" button.1 vote -
Yellow help icon
i love the help you guys provide, really great.
Suggestion.. The yellow circle that you open and drop down.
1) can you move it to the header, and if there is a pending message show the yellow circle with a number in it ( number is count of pending messages )
2) can you make it a separate window model? typically when i am chatting, i need to see the entire screen and the current pinned model is usually in the way and i need to click the arrow to get rid of it.
If i could drag the window…1 vote -
Integrate with Linear
Linear is quickly becoming the new Jira for today's technology and engineering teams. It should be considered an important integration.
2 votes -
Ability to turn rules/processes off as needed with ability to rollback
There are times when need to update data or load data into Salesforce org and need to turn off rules or processes before updating data or loading the data. When doing a data deployment, GearSet has this ability, and I would like to have this ability to do this without a data deployment. Ability to turn off Validation Rules, Required Fields, Restricted Picklist, Workflow Rules, Flows/Process Builders, and Triggers one by one or turn off all. Then roll back once finished updates.
1 vote -
1 vote
-
"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.
3 votes -
When cloning a deployment, also clone the test settings
When I'm cloning a deployment, if in the original one I have selected specific test classes, by default have those selected again in the clone.
Often you either need to repeat a deployment, or you'll deploy several times between instances, with the same tests.
1 vote -
Make filter to search through all the components which are hidden under 1st level and expand the components
Can I ask Gearset team to add filter in compared components to search through all the components which are hidden under 1st level (e.g. custom objects or profiles).
For example, in the filter to compare metadata I selected certain custom tab (in the profile the access to the tab was deleted), also selected certain profiles, but serching through the compared metadata list I spent hours and did not manage to find those components for deployment package.
The same is for object access. I selected certain object, selected certain profiles - and again, it's a hard quest to find necessary components…3 votes -
Release Branches
If I create a Release Branch from UAT, I no longer need all the individual Feature branches.
Inspired by Gitflow and the current Gearset Expanded Branching Model.
Currently: The Expanded Branching Model will create a Feature Branch PR to main for every Feature branch that is merged to UAT branch.
Desired: When I create a Release branch from the UAT branch, then Gearset should close all the current Feature Branch PRs to Main Branch - if and only if the Feature branch was already merged to the UAT branch.
This is related to branch pattern matching because…
1 vote -
Gearset doesnt support Versioned Dataraptors for vlocity deployment
Gearset doesnt support Versioned Dataraptors for vlocity deployment.
Details provided to Valerio Chang1 vote -
Add ability to run sfdx force source status command for metadata deployment
It would be great if, when comparing an org to a repository, we could run the status command (sfdx force:source:status) to see the difference between a Salesforce org and the repository.
This command provides a list of files that changed to the user instead of performing a full (and tedious) comparison between the source and the target.
Having a list of changed files would make it easier for a user to see what change they made in an org, make it easier for them to not miss a file and would make comparison so much faster (since you would be…
1 vote -
Link to the Salesforce Validation in Progress from the Pipeline
When I deploy using the standard deploy interface, there is a link that allows me to view the deploy progress in Salesforce.
In pipelines, I would like this same feature. When a deploy has been running for a while, it's useful to know where it is in the process and a quick link would be quite nice.
2 votes -
Branch Pattern Matching
I want to use branch pattern matching to map CI Jobs to specific types of branches in my repository.
main
uat
dev
feature/*
release/*
hotfix/*
chore/*Each of these branch types can have different CI Jobs associated with them. Or in the case of a chore/*, maybe I want those branches to Skip CI Validation because it is an ops branch that doesn't contain any Salesforce components.
1 vote
- Don't see your idea?