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.
1361 results found
-
gearset doesn't seem to pickup date of change for custom field and custom metadata.
gearset doesn't seem to pickup date of change for custom field and custom metadata.
2 votes -
Filter option: not containing, eg. rather than filtering for 'custom field', filter by components not a 'custom field'
A better example might be I don't want to see anything that has the word 'contact'.
1 vote -
Ability to differentiate between scheduled metadata deployments from validated packages and non validated packages
Under Deployment History
All scheduled packages should appear. This is not the case today, validated packages that have been scheduled appear under validated packages with a Scheduled Date but not under Deployment History
Scheduled packages should have a link to the appropriate Validated package if any.
1 vote -
Change the Metadata Filters and make them first class
I would like to see a change to the metadata filtering in general.
Filter management has become a important part of our devops process as we seek to lower our comparison timing.
Instead of having it at the bottom corner of the compare screen, move that section to the middle of the compare screen.
In addition, add a side bar specifically for filters that allows you to edit or delete them as well as change the sharing between personal and team. I have example screenshots for suggested layout changes here: https://faef.box.com/s/frse8jnvqsxbl8ue05x641j3wlga1quy6 votes -
Allow serial deployment instead of parallel
When executing a data deployment, an 'Unable to lock row' error can occur if multiple transactions try to lock the same record in Salesforce.
Because the batches are executed parallel, the chances of getting this error high, depending on the situation.
For example the master record in a master:detail relationship will always get locked when a DML is executed on the child record.
If two batches are executed at the same time and they both have at least 1 record that references the same parent, then a locking error will occur.6 votes -
Warn on Master/Detail deployment even without comparing Custom Fields
If you compare Custom Fields and try to deploy something in an Object that is in a Master/Detail relationship without including the Lookup field, Gearset will warn you that the deployment will fail.
However, if you don't include "Custom Fields" in the comparison, (for example just comparing Validations) and try to push it, you will hit an error:
"Cannot set sharingModel to ControlledByParent on a CustomObject without a MasterDetail relationship field"
Gearset could easily warn the user on this when trying to push a Validation Rule on a MasterDetail object, even if Custom Field was not added to the comparison.
2 votes -
create a Default Value setting on Source Control & Connections
Reading the previous suggestions this might be a bug.
Where a user has multiple connections to Github, Bitbucket etc. It would be good to be able to set a default connection.
It is suggested that when you go to Compare, the last selection should be displayed. But I am not seeing that happening?
I would expect the default Source to display, no matter what Compare I and setting.
1 vote -
Include validation rules and triggers of managed packages in 'Compare and deploy disabled rules'
When configuring a data deployment there is an option to disable validation rules and triggers on the target org. However the validation rules of objects of a managed package don't get included in this comparison. Triggers of a managed package are also not included.
I'm not sure if it will be possible to disable the triggers, but for validation rules this should be possible.
3 votes -
Show data hosting option chosen for an account
It would be great to see the chosen data hosting option for an account in the 'My Account' area. Without it security audits will not be able to verify what setting was chosen and will have to rely on documentation held elsewhere.
1 vote -
Include code coverage in deployment report
Hi,
I want to use the deployment report to monitor your progress towards improving the quality of our code.
So I need code coverage to be included in this report.7 votes -
Add an option to disable Problem Analysis for CI
When running CI jobs, we can create a problem analysis template to control what potential problems can block a deployment.
For deployments from SF orgs to Git, many of the problems being analysed are just irrelevant (e.g. users don't exist in the target, because the target is not Salesforce).
Although some options can be switched off via templates, the list is not comprehensive. So, it would be great to have an option to switch off everything, or a built-in template of "no analysis".
When production is the source of truth, we just want all the metadata to get copied into…
1 vote -
Allow Package Cloning between Saved Comparison Pairs
Please allow us to select a comparison pair as the source/destination when cloning a package. This will make it much easier to select the source and destination when cloning a package, and reduce the risks associated with accidentally selecting the wrong repo or branch or sandbox.
2 votes -
Add a filter in monitoring job to exclude changes done by Gearset
To help identify changes done manually to the org it would be nice to have a filter which excludes all the changes done by Gearset deployment.
2 votes -
Improve error message when XML is not properly escaped
When I choose to compare metadata with my source as my VCS, there was an "&" char in the recordtype XML definition file.
<values> <fullName>Food & Beverage</fullName> <default>false</default> </values>This threw an error and there was no support and no explanation at that time.
I suggest you to improve this error message.
Message I got:Could not parse the XML for 'force-app/main/default/objects/Lead/businessProcesses/Buyer.recordType-meta.xml'. Error occurred at line 71. Further details: An error occurred while parsing EntityName. Line 71, position 29.
File, line and position it's ok. maybe a link to Gearset docs with walkthrough with this probable cause when a parsing…
1 vote -
Add the ability to order/chain overnight jobs
Gearset offers various automated jobs that run overnight e.g. Org Monitoring Snapshots, CI Jobs, Unit Test Runs.
it would be great to be able to set an ordering on how those run for any particular org. For example, a natural order for the night jobs may be:
- Monitoring Snapshot
- CI run
- Unit testing
This means we have a backup before making any potential CI changes and the unit tests show the results after CI. It would also allow us to make sure that the jobs don't clash.
Ideally, we'd be able to do this without just specifying exact times to…
2 votes -
Delete comparisons
Be able to delete a comparison run with wrong filters or just keep the latest comparison
1 vote -
Mass deletion of data from backup
We want to know how to automate the deletion in backup system.
Common use case is deletion of customer data due to legal compliance.
1 vote -
Add the concept of Master seeding object
One great feature to have, would be the possibility to identify a Master object from which the filters applied on it would be applied on all dependent objects automatically.
2 votes -
Delta only validation CI jobs
Idea is to have the Delta CI for Validation only Job, so the as well, so the validation process will become faster .
The option of validating a PR in the deployment job does the same task, but is comparing too many items of metadata and it is taking too long.
14 votes -
Allow 'OR' combination for multiple External ID's in Upsert operation
Gearset allows the selection of multiple External ID's in an Upsert operation as part of a Data Deployment.
However, the system implements an 'AND' combination across all the external ID's specified on the object.
Effectively, ALL external ID's need to be present on the target side for the match to be identified and record upserted. If all external ID's are not present, the system performs an Insert on the target org.Please allow an 'OR' combination across multiple External ID's. Arguably, this should be the default option, but at the very least, a user needs the ability to decide how…
4 votes
- Don't see your idea?