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.
241 results found
-
Support merge fields in outgoing webhooks of CI jobs
When sending an outgoing webhook, I'd like to be able to include if the job succeeded, the name of the job etc.
11 votes -
Add default compare filter - Code changed by me today, changed by me last 7
A super common comparison done by a developer is to see only the Apex changes done by that developer today , or in the last x days
Since the last changed dates on Apex (VF, triggers, components) is super reliable whereas it is useless on Custom Field/Workflow), the suggestion applies only to Apex or code-type changes
Gearset would fetch only those code items changed in the last x days, then present in the difference viewer the changes pre-sorted in descending date order
This feature would eliminate multiple clicks just to deploy a handful of recently-made code changes in the comparison…
5 votes -
When running "Compare and Deploy", or via a similar mechanism, allow the target to be a local zip
In rarer situations where I need to make some manual adjustments to the metadata XML for a deployment, I'd like to be able to download the metadata to adjust it. Today you need to go through a compare, and at the end, you can download the package, but this can be problematic, since you have to choose the target org, there need to be differences, etc.
Instead, it would be useful to just choose the source org, select the metadata items, and save the package, without a target org needed.
1 vote -
Allow save into a draft deployment after Refresh Comparison
Use case:
Source is master, target is org
Create draft deployment between master and org; Save
...time passes, new items are added to master
Open draft deployment
Refresh Comparison to see new items in master
Select new items
Click Save Draft Deployment --you have to create a new version (and no obvious way to even see the current draft's name without opening a new tab)Seems like you should be able to save back into the same draft after refresh comparison (or at least have option to do so).
When you create a new version of the draft; you have…
16 votes -
Pending Validation - Copy from Pending Deployment
Similar to "Pending Deployments" It would be nice to see pending validations. We have several users in gearset, so if we are trying to validate something while someone has already initiated a validation, we receive the error that set up has been locked. So prior to validating a package, it would be great to check if anyone is in the process.
1 vote -
Allow changing of public group membership via Gearset
Right now, the only way to edit a group's membership is via the API (users or groups only) or the UI (additionally allows roles, roles and internal subordinates, etc.). Please allow the editing of group membership of public groups.
3 votes -
Allow option to select certain test classes to NOT run. Include an exclusion list of tests not to run
When deploying code, it would be nice to have an option of having an exclusion list of test classes to not run.
5 votes -
Test run details: show failed tests tab first
When user clicks on test run details, Gearset defaults to the successes tab. But no one clicks on test Run details to see successes; they want to see failures. Default tab should be failures, especially if non-zero
Saves user a click and supports DWIM - "do what I mean" when clicking Test Run Details
1 vote -
Enhance capabilities around 'co-administration'
In our organization we have a couple different salesforce admins that are administrating the salesforce development pipeline in which several developers are making changes and deploying them via gearset. Right now it seems cumbersome/duplicative to do this particularly around the area of adding a sandbox org and then managing permissions of the developers to that sandbox. It would be nice if there was a way for one admin to connect the sandbox, grant the other admin "Owner-level" access to it, and for the two admins to have a shared view of the user access to that org, so I can…
2 votes -
Ability to chose multiple targets for a deployment
It would be nice to be able to deploy to multiple environments all at once from one source.
33 votes -
Show the Created Date and Refresh Date on the Draft Deployments
I understand the Draft Deployments are snapshots from when they were created or last refreshed. Is that right? Please show these fields on the Draft Deployments page.
3 votes -
More Details for Open Draft Deployments: Show Name & Refresh Date
When you open a Draft Deployment it would be great to see its name on the deployment page as well as its refresh date. I understand that when you open a draft deployment you're seeing a snapshot from when it was created or refreshed.
1 vote -
I have so many connections and jobs, is it possible to have group them (in future release?)
I have so many connections and jobs, is it possible to have group them (in future release?)
2 votes -
Please, please, please get US FedRAMP approval.
The ability to use this product for CI/CD and various other use cases in the US federal space would be a huge win for many agencies. I know the FedRAMP process is quite arduous, but the contractual potential here is pretty massive.
5 votes -
Add deployment support for Macros
Macros deserve to be added to source control yet there is no way to do this with Gearset:
1) Data feature (paid add-on) doesn't deploy to/from source
2) PRO/Enterprise can't source/target deploy Macros because it is not available with the Metadata API.Since macros represent some debugged logic, managing in source control makes sense. Curiously, SFDC has chosen to make Documents available via Metadata API but not Macros
4 votes -
Allow for custom metadata permissions to be included with a single click when custom fields are being deployed
For example; when adding new custom fields, you generally have to add the permissions as an additional line item to the deployment. Having a checkbox or something that will have gearset automatically add the permissions associated with the metadata currently in the deployment list would speed up the process. Users should also be allowed to deselect lines that were automatically added.
16 votes -
Build Comparison Manifest from pull request
It would be cool if the custom deployment configuration could be driven from a Pull Request . For example, in GitHub, the Pull Request knows which files were changed and approved. Why not use that list to instantly populate a comparison to create a deployable manifest to go from source control to org?
15 votes -
Restrict source orgs
For example, deployments to a production environment should only come from the master branch of our git repository
4 votes -
Deploy parts of Settings
It would be nice if you broke up the settings into smaller subcomponents. For example the Security settings would be more useful if you extract out the password policy changes so we can pick and choose what Security settings we need. I thought of this concept similar to how you break up profiles into sub component. This could get noisey in the list of changes so an alternative to that could be to bundle it under components like how CustomObjects work.
2 votes -
Indicate whether a Validated Package is enabled for Quick Deploy
T0 - You Validate a package to PROD (run all tests)
T1 - You or someone else does a deployment of something else, no matter how minor, to PROD.
T2 - You click Deploy of the Validated Package from T0, all the apex tests are rerun. This is by design per SFDC yet Gearset doesn't tell you in advance that Quick Deploy is not available. Something you think will take a couple of minutes now takes 30 minutes or more. You think you screwed up or Gearset is broken
Suggestion: On Validated Packages page and on the page of a…
3 votes
- Don't see your idea?