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.
1355 results found
-
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 -
Deactivate email deliverability on Data Deployment
User email are masked in Sandboxes and we can mask Contact emails as part of the data deployment. This still leaves the Org Wide addresses as valid emails. If there is automation that is generating emails related to the data that is loaded, they will be delivered to the Org Wide Addresses.
It would be useful if the same script that is deactivating validation rules could set email deliverability to systems emails at the same time.
In the even that email deliverability was set to all emails in the Sandbox and not adjusted before the data deployment we would have…
5 votes -
Update Metadata Change Monitor Report
When you update the change monitor report metadata filters and include new metadata types, the next monitor report shows all the newly added metadata as "New Items" on the report. Although not a big deal it did cause an alarm for us not realizing it was due to the change we made prior. It would be a "nice to have" feature if either you don't include the newly added metadata types as "New Items" on the initial report or flag them and have a visible cue to indicate the items were a result of newly added metadata items on the…
1 vote -
Force selection of fields to use instead of selecting id as default
In the select related objects page, Gearset selects id as the 'fields to use' field. If we are deploying a large set of data and by mistake do not change the 'fields to use' field then we end up creating duplicate records for Upserts. Would be great if there is an option to enable or disable the default selection.
1 vote -
For failed CI job runs, develop a way update to the job status
When for whatever reason, jobs can get job stuck in status "Deploying".
The real deployment task is already successfully finished in the org, so I would expect that the status of the CI job would be "Succeeded".
I was assured that in 24hrs the status of the job will automatically reset, but can we have also a way to force an update to the CI job manually?
Note: The "Cancel running CI job" button is visible and clickable, but doesn't do anything with this stuck CI job.
1 vote -
Preview of records for data deployment
It would be great either via the UI or a downloadable file/CSV, if we could see all the records that will be migrated in the data deployment. We're able to see the list of successful or failed records after the fact, it'd be nice to see the list of proposed records before hand. This would help identify if we're in the correct ballpark, say 500 records vs. 5000, and not knowing that until after the deployment gets attempted.
4 votes -
add an account based autonumber field to deployment that could be used as a friendly reference
This could be automatically prefixed to friendly name of the deployment.
Sth like "000035"
Could be a simple counter (that I see you have implemented "This is your NNth deployment...").
If the autonumber would pop up automatically then I would not need to figure out a reference and type it myself.
Currently, info that potentially could be used: datetime (too long) , url (way too long)
2 votes
- Don't see your idea?