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.
1308 results found
-
Option to download problem analyzer template
Option to download the problem analyzer template so users have an option to add it to the custom github actions scripts to run CI validations for their own delta comparisons.
1 vote -
'Continuous integration' menu item links (redirects) to Deployment Pipelines
When I click on 'Continuous integration' in the left menu it goes (redirects) to Deployment Pipelines (https://app.gearset.com/deployment-pipelines?pipelineId=xxx) by default since a week or so! 👎
I just want that menu item to keep on going to the 'Continuous integration dashboard' (https://app.gearset.com/continuous-integration).
What's in the name (of the menu item)! 😉1 vote -
Sort or Filter Active CI Jobs
Currently, there is no great way to filter out old/inactive CI jobs from the Active CI jobs. This poses a problem as there are situations where we have replaced CI jobs in the past, or created/disabled test jobs. Currently they clutter up the Continuous Integration Dashboard, but it would be nice if we could hide them so we don't have to delete them and lose their history.
1 vote -
link deployment to a salesforce case
The ability to link a Gearset deployment to a salesforce case record. If an org uses cases to track a bug or feature, this feature would close the loop from that case to the gearset deployment.
I understand that there is a post to chatter functionality but it would be nice to target a specific case for auditing purposes.
1 vote -
Rerun faild tests on the unit tests screen
It would be nice to be able to rerun just the failed tests with a separate button, when debugging scheduled tests
1 vote -
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 -
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 -
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 -
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
-
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 -
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 -
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 -
Pipeline CI jobs where deployment is disabled should capture validation job history
If you have a Pipeline CI job configured to be Run Job = disabled; you can still promote PRs and run validations (which is great). But the validation job history is not preserved under the CI job. In fact, AFAIK, it can't be found at all except for the current promotion's vcalidation
This would enable one to diagnose validation fails - perhaps due to problem analyzer automations. It would aid in communicating with support (as such validations could be shared)
1 vote -
Ability to test restoring of backup data periodically
It will be nice to have option to automate and test restoring of backup data periodically into a sandbox. Since it is going to be restoring production data to sandbox, there should be options to restore chunk of production data (due to the storage limitation with sandbox) and the metadata.
1 vote
- Don't see your idea?