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.
993 results found
-
Implement public key authentication for source control
Implement public key authentication for source control.
Allow Gearset to generate a public/private key pair, and expose the public key for use in authentication to source control.
1 vote1 comment · Integrations and connections (Jira, source control, DX etc.) · Flag idea as inappropriate… · Admin → -
Clone deployment with favorite source:target combos
We use Clone from Deployment History quite often. A typical use case would be:
Deploy from feat org F to branch
Do PR & merge to /master
.. CI runs
Upon successful CI
Clone deployment with source = master and target = QA org
Upon successful UAT
Clone deployment with source = master and target = PROD orgRather than having to re-enter on the Clone dialog the source and targets, since they are always the same, it would be nice to "favorite" sources and targets (assigning a favorite name) and then reusing those favorite names on the Clone dialog
1 vote -
CI Validation Job report should show version of metadata API used for CI
A nice-to-have UX feature would be to echo the metadata API version used in the CI Job on the Validation Errors report (or any CI report). This can be used to aid in troubleshooting
This is especially helpful when a source or target org is using a Preview sandbox
1 vote -
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 -
Zapier Integration
An integration with Zapier will allow more customizations options for how we can integrate with other tools, such as Manuscript (fka FogBugz).
1 vote0 comments · Integrations and connections (Jira, source control, DX etc.) · Flag idea as inappropriate… · Admin → -
Optimize comparison list view
The comparison view contains a list view in a scrollable area with an line item for every metadata item in the comparison. Depending on the comparison, this list can be exorbitantly long (10k+ lines). Displaying this many elements on screen is extremely inefficient, and causes browsers to lock up when selecting the "check all" check box (because it results in thousands of incremental manipulations in the DOM). This issue also causes mobile browsers to crash when more than a thousand or so items show in the comparison results.
There is a common pattern for handling long lists like this, in…
1 vote -
Cache deployment inspection results
It would be great if deployment inspection results were cached, such that the results for an identical set of metadata are available without spending the time to recheck everything.
Use case: A comparison is performed and all changes selected. Deployment inspection is performed and recommendations are made for items to add/exclude. I select a subset of recommendations, and move forward with validation. The validation fails. The same comparison is reopened and again all metadata is selected (with the intention of selecting more of the add/export recommendations resulting from the inspection). At this point, the inspection is rerun, even though the…
1 vote -
integrate with Atlassian Stride for notifications
Gearset's ability to send notifications to Slack is great. I'd like a similar ability to send notifications to Atlassian's Slack alternative - Stride.
1 vote1 comment · Integrations and connections (Jira, source control, DX etc.) · Flag idea as inappropriate… · Admin → -
Avoid spurious Analyzer message when deploying external objects (e.g. Foo__x)
If you create a new org, add an External Data Source, add External Objects, and deploy to a target (source control), you will get this spurious analyzer message:
"Some standard object fields which don't exist in the target organization are being deployed, which indicates they might use features not enabled in the target. You need to remove these from the deployment, otherwise it's likely to fail."
and all your external objects are enumerated, e.g.
Ordersx
Customersx
...These are not standard objects, and, as they are new, would of course not be in the target. Analyzer is being…
1 vote -
Add Run all tests except .... configuration in CI job
Our CI jobs take way too long (1000+ tests) despite heroic efforts to use ApexMocks. As our org contains a bunch of unmanaged packages with known class name prefixes, and these constitute at least 10% of the total tests; we could get back 10% of our life if we could exclude these from the "run only your tests"
For example, we would want to exclude running any tests in classes that start with "fflib" and "sfab"
A variation of this would be to run a specific testSuite and it would be our responsibility to keep the testsuite up to date
1 vote -
Ability to have automated process to maintain field list in Production environment
With GDPR, companies are required to provide justifications for all data that they collect. In Salesforce this means being able to identify why all fields in the system exists, categorize fields as PI, and provide business justifications. The ability to keep a list of current fields in a production instance of Salesforce that includes alerts when new items are added, or ability to sync that list out to another tool like Smartsheet, where other business users like a legal team would have visibility, would be incredibly useful.
1 vote -
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…
1 vote -
Allow repeat/redo deployment from Deployment History
Use case:
- Deploy from source to target
- Some testing (or possibly PR review) in target requires fixes to be redeployed from source to target
Currently, you either do a new Comparison or clone the Deployment and re-enter the source and target. In either situation this is tedious.
Why not add a "Redo" button on the Deployment History that uses the same source/target? Place it next to the Clone button?
Or, in the Clone button, default the source and target to the same as the selected Deployment? (which would also be useful)
1 vote -
Add an option to use a custom "Gearset format" for the source control output
The XML that comes from Salesforce is weirdly bundled together. When changes are made it's really hard to reconcile two branches in source control when merging.
When comparing, Gearset nicely decomposes changes into smaller chunks. So instead of putting that back into the usual XML, an option to store that "internal format" and even just stick it as JSON or similar.
After all - it'll be Gearset reading it back in to compare to an org next time, and smaller changes will be easier to merge as they won't conflict inside horrendously large XML files
1 vote -
Better error message when refreshing draft deployments created by another user
Currently, if source control is either source or target and User A creates a draft deployment bit user B wants to refresh that draft deployment, you get an error message: "Error occurred during operation: Determining API versions - An unknown error occurred."
As this capability isn't currently supported by Gearset, there should be an error message when the refresh comparison button is clicked saying" Refresh is not possible when Source control is involved except by original creator of the draft deployment"
1 vote -
Filter Notifications for Non-CI Deployments By Successful or Not
When I do a deployment that is not a CI deployment, it can send an email. But the email goes out regardless if the deployment is successful. I would like to be able to send the email ONLY if the deployment is successful.
1 vote -
Allow renaming of picklist values instead of creating new and deactivating
Currently, when you rename existing picklist values in the source org (including renaming the API name of that value), Gearset will deploy this to the target org as a new picklist value and deactivate the old value. This means we have to manually delete the value in the target org and specify which value to use to replace on existing records.
It would be great if Gearset could give the option to map a picklist value in the source to a picklist value in the target and allow a rename of the value in the target.
1 vote -
Add an Ignore option for change alerts
Sometimes metadata comes back from Salesforce in a different order, which makes it look like there was a change when there really wasn't any. It would be nice to have a way to flag such comparisons as Ignored so I know I looked at them and decided that they didn't need to have any further action.
1 vote -
Issue with Namespace while deploying from Org A to Org B
the namespace if referred in code, we try to deploy to target Org, the target Org will not have the same namespace name, or will be a different namespace, it gives errors, can something be done to fix this?
1 vote -
In comparison mode, remember whether I want to see the XML view or a friendlier view of the object I'm looking at.
I noticed that the non-XML option label changes depending on what type of object I'm looking at. Regardless, if I select the non-XML option in comparison mode, I'd like the site to remember that option during my session so I don't have to keep re-clicking the non-XML option for each line item.
1 vote
- Don't see your idea?