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
-
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 -
Trust Site
Right now, Gearset is down and we cannot use it. It would be good to have a trust.gearset.com site that shows what is going on and what the team does to fix the issue...
5 votes -
When pushing Workflow rules and associated actions, gearset mistakenly says target objects do not exist
When pushing work flow rules and associated actions, if you do a compare with only workflow, then gearset prompts an error indicating that the target objects do not exist in the destination and that the rules should be removed from the package for the deployment to be successful. In this case, it told me Account, Event and Opportunity do not exist in the target. Including other metadata from the referenced fields resolves the issue.
4 votes -
Restrict source orgs
For example, deployments to a production environment should only come from the master branch of our git repository
4 votes -
Allows admins to limit the available branches of a repository
When connecting a source code control system, quite often an integration user account is used that may also be used for other parts of the enterprise. Please allow admins to restrict the available repositories and branches so that users can only run comparisons for the branches they should actually have access to.
5 votes -
Add an auto-save feature while building deployment packages
As Gearset is run through a web browser, if the browser happens to freeze while a package is being built, you don't have the opportunity to save it as a Draft Deployment. An auto-save feature would allow someone to pick up where they left off, or when the last auto-save was done, without having to start from scratch.
52 votes -
Improve PermissionSet comparisons by providing an option to ignore fieldPermissions when their editable/readable are set to false
Current Metadata Behavior:
When a new object is added, objectPermissions are only added to a PermissionSet only if one of allowCreate, allowDelete, allowEdit, modifyAllRecords, viewAllRecords are set to true
When a new field is added, the new fieldPermission is added to all PermissionSets by default (with editable and readable set to false).
NB. PermissionSets are additive in behavior and can only open up access not revoke. Values of false have no meaning and are only noise.Current Gearset Comparison Behavior:
Comparing PermissionSets show these new fieldPermssions as New Items even when default values for editable, readable are set to false.…9 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 -
Enforce code coverage limits on CI jobs
Please set it so that we can force a code coverage check on deployments (including CI). I'd like to verify on the lowers before going through to production. Might be able to do this with test cases but should be able to on deployment.
5 votes -
Scheduled deployment freezes
Prevent deployments during certain periods of time for a team or for production environments
10 votes -
3 votes
-
Allow (restricted) editing of source XML to add deployable properties that can't be fetched via Metadata API
Example:
It is impossible with OOTB Gearset to deploy an autonumber field with a starting number and optional populate existing rows. Why? Because the SFDC Metadata API as of V42 doesn't allow fetching of these two properties of the CustomField object:<populateExistingRows>true</populateExistingRows>
<startingNumber>1</startingNumber>Once in source, they'll deploy just fine to the target org. Note that changesets support this feature.
The workaround, which is to deploy to target branch and then edit target branch is sort-of-OK but it would be nice to modify this in the source. Of course, if you Refreshed Comparison, your edits would be…
2 votes -
Ability to copy Territory models from one org to another
It would be great to be able to copy Territory models from one org to another, as per this request in the SFDC Community...
https://success.salesforce.com/ideaView?id=08730000000DgemAAC29 votes -
Ability to manually hide/filter component differences by single flag
When reviewing comparisons it would be extremely helpful to have the ability to manually 'hide' a component difference (e.g. a single flag to filter out, ignore, or even 'grey' a component differences) once you have a) reviewed the XML and b) determined you do not want to deploy or view that component in a saved draft. I.e. a third state that is not simply 'selected' or 'deselected'.
Current filters by component type, name, et al. don't accommodate for wanting to hide a known component difference (e.g. like an Apex class still under development) so that you can only see remaining…
2 votes -
Allow for selecting which repositories to display for github in org settings.
It would be helpful to be able to select repositories to display in the selection under Manage Orgs. Some of our repos in Github aren't related to Salesforce deployments, and filtering those out so they don't even show in the list would be really helpful in getting to selections faster.
10 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 -
Show # differences found in comparison display
It would be a nice feature to see the number of differences for each item from the perspective of the source org vs target org.
3 votes -
When a Picklist Populates, Don't Default to the 1st Value, Default to Blank
When I choose my destination, the system defaults the picklist to the first item on the list. Instead it should populate the list but don't pick a value.
For example, when I choose destination = BitBucket, it then takes a moment to load available branches. It takes a little bit so I go on and start to configure the metadata types. Meanwhile, Gearset populates the list and sets the value to the 1st branch on the list, in my case, feature/helpdesk. It should leave the value blank and make me pick.
This has resulted in me running long-running comparisons, and…
3 votes -
Reuse Deployment Package (clone) should use sticky "Source Repository"
Use case:
1. Compare and deploy from repo-R/master to org A
2. Clone deployment from repo-R/master to org BUnfortunately, when the clone deployment displays the dialog "Reuse Deployment Package"...
a) When you select GitHub, the dialog doesn't default the repository to Repo-R but instead displays a picklist of all possible repos the running user has access to (in our case that is 100+)
b) Better would be to remember in cookie the repo the developer last used and default to that choice so scrolling through 100 items is not necessary.2 votes -
Allow comparisons of a single commit from a VCS
Currently, you can select a VCS repo and branch to use for comparison. It'd be great if you could select a specific commit from that branch, so that you're only looking at an atomic set of changes. This would allow for fine-grained comparison and deployment of changes.
10 votes
- Don't see your idea?