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.
1439 results found
-
Default to Object View
Option to default to Object View vs XML for metadata types that have it available
9 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 -
Display which apex triggers have low code coverage if a deployment fails
It would be great if Gearset can surface which Apex trigger has 0% code coverage when a deployment fails.
9 votes -
Provide option to disable parallel apex testing in Scheduled Tests
Scheduled Test runs can fail due to UNABLETOLOCK_ROW errors. This is due to what amounts to a bug in SF: accessing public custom settings in tests which are run in parallel can cause deadlocks. Really, the tests ought to be isolated from each other, but they are not. See:
The workaround in SF is to disable parallel apex testing.
If Gearset could do that during the scheduled test run, it would prevent false test failures.
I guess I could change the option on the SF org, but sometimes parallel testing is useful, so I wouldn't want to…
9 votes -
Allow filtering of records for data deployments via a SOQL
Would like to be able to run a SOQL to select the records to base a data deployment from, in many cases we are trying to build some test data that matches specific scenarios based on fields on parent or related objects.
The current selection of field filters doesn't give us the flexibility we need. For most of our data deployments to sandboxes today we run a data load in prod to set a field to true on the base object from a SOQL and then use that field to filter in the data deployment.
8 votes -
Invoke Run Anonymous Apex against target in CI Job
Team,
Can you please add Run Anonymous Apex option in a CI Job ?Step#1
In this scenario from Developer's end they should add pre scripts in a.txt file and add post scripts in b.txt file in their Source ControlStep#2
How it should work
- It should allow the CI job to run Pre and Post Deployment scripts
- Pre Deployment scripts should be picked up from Source control a.txt file and Post
Deployment scripts should be picked up from Source control b.txt file
- Post commit the diff of commit should identify what are pre and post scripts…8 votes -
Cleanup Layout Assignments
When you rename a Layout, the previous Layout Assignment won't be cleaned up on the Profile.
This should be cleaned by the Repo dependency cleaner.8 votes -
Approve Pull Requests from Gearset
Currently you have to navigate from Gearset to Github using the link from the Pull Request to approve a Pull Request. While functional, this requires going to an external system for an important Git functionality. This also creates a bit more complexity for non-technical users. If we could approve PRs directly from Gearset, that would be awesome!
8 votes -
Ability to audit what users have done in Gearset
Hi, I suggest there should be a feature which monitors what the users within your orgs have done in Gearset. As we can currently are able to view both comparison and deployment history, however this does not give an audit trail of who has changed what and where.
For Example, the ability to review changes that a user has made to gearset comparison filters.8 votes -
8 votes
-
Users should be able to specify test classes and save them to draft deployments
Users should be able to specific and save test classes in the comparison stage so they can be saved in draft deployments. Seems like a waste of extra steps to unclick tests and select tests over and over as you work through a deploy.
also when deploys are combined, they would get all the test classes, again, saving lots of time.
8 votes -
Bash scripting
Add support for bash scripting. This is one of the most powerful features of Jenkins and something that would make a huge difference in Gearset.
8 votes -
Keep list of specified tests
When choosing specified tests to do a validation, let's say from a comparison that was created from a bunch of drafts that were combined, the pop-up will show the specified tests that were chosen originally for those drafts that were combined. That is awesome and is exactly what I want.
The problem is the "Fetching test classes from Salesforce" then occurs automatically and replaces that list with the full list of test classes, and check the boxes for all of them, replacing my existing list. That means I have to go back and choose my list of specified tests again.
8 votes -
Allow Data Deployment to filter lookup fields on fetched data
Currently, when doing a data deployment Gearset will let you know of all the referenced objects from the object you selected. What it doesn't do is the opposite of that - let you know all the objects that reference your object with a lookup.
It'd be great if we could add a filter to utilize some data pulled in a fetch/query during data deployment.
ex. field (TeamMember.ProjectLookup_c in {returned Project results in query in previous step of data deployment).
8 votes -
Add Upload CSV functionality to create an upload template for CPQ deployments
For CPQ Deployments add an "Upload from CSV" feature where a user could upload a file with specific External IDs across multiple objects to tell Gearset what to migrate in a single click.
For example, the user could list the Object API name in Column A of the sheet and the External ID in column B and then Gearset would parse this and create a Data Deployment based off of those records specifically. This would be incredibly useful for any CPQ deployment where you need to only deploy specific records not the entire object!
8 votes -
Link to test runs in Slack messages (or Slack messsage customisaton/templating)
I have automated test jobs post about failed tests to our Slack. I want the posted Slack message to include a direct (though maybe shortened) link to the "Test run details" so that when we see Gearset telling us about some tests starting to fail I would be one click away from seeing a view of failed tests the message is talking about.
Next/bigger step would be a way to shape the Slack messages ourselves. The most basic templating setup where I could write my own Slack message with some placeholders like {{instancename}} or {{failedtests_link}}..
8 votes -
Add option to suppress managed custom fields in comparison results
When comparing Custom Objects that contain the managed custom fields there is no way to suppress the managed custom fields. The fields would show up in the comparison results even without being requested. The problem analyzers then highlights and remove these managed custom fields.
This is cumbersome when repeated and makes finding genuine differences we care about more difficult.
From the problem analyzers, it sounds like Gearset is able to identify the managed custom fields. Therefore could there be an option under [Include managed package] in the Custom Filters that allows the suppression of known managed fields in comparison results?
8 votes -
8 votes
-
Here's the best solution: Be able to quickly select the custom objects and standard object custom fields AND only the related metadata items
Would like to be able to quickly select the custom objects and standard object custom fields AND only the related metadata items to make then function correctly (permissions, layouts, field level security, etc..)
Then we could go back and migrate all the process automation stuff - workflow rules, flows, trigger, etc..
It always starts with the data schema first. We need a quick way to see what is different between two orgs and get that synced first
8 votes -
Send a link to the report in the notification
It'd be nice to have a link to the report included in the notification for any scheduled monitoring, test run or deployment/validation.
8 votesThanks for the suggestion.
When you run a deployment, the deployment success email contains the PDF of the deployment report, as well as a link to your deployment history to view the full information.
For the test/change monitoring emails, what sort of report would you like to see? Would you like to see the full information on tests run or just a summary of key stats?
We don’t currently provide the ability to export PDF reports for our change and test monitoring jobs in the same way as our deployments, but it’s something we’ve been thinking about putting in.
Thanks,
Jason.
- Don't see your idea?