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
-
FLS selection for Source control
while deploying a field to source control. we just want to move profile FLS of that only field. FLS was not displayed on the components drop down of profile. we are only able select profile so that whole object's FLS are getting deployed to the Source Control.
5 votes -
Trigger a data deployment from a CI job
When we pull down a version between our local and staging environments. We would like to also automatically pull in the testing data from another project.
As one of the things we are trying to setup is taking a version from Prod then running GhostInspector through our core flows. Ideally every 4 hours we take a backup from metadata + locked down actual data. Then run tests against it.
3 votes -
2 votes
-
show which deployment each metadata was a part of when doing a bulk clone.
When doing a bulk clone, each metadata should show what previous deployment it was a part of as to allow us to verify that the bulk clone worked. Another use case is that it would allow us to find a deployment we know has changed and be able to remove or change the metadata quickly.
1 vote -
Extend the ability to add and delete in a single deployment to all metadata types
We just came across an issue in which we were deploying an HTML email template that had been moved from one folder to another in the source environment.
When deploying, only the delete happened on the first deploy. I needed to do a second deploy to handle the addition.
While probably not a common case, it's certainly important as the initial deployment reports that the addition was successful.
1 vote -
Allow option to select certain test classes to NOT run. Include an exclusion list of tests not to run
When deploying code, it would be nice to have an option of having an exclusion list of test classes to not run.
5 votes -
Org Management/Oversight Dashboard
I would really benefit from a dashboard option. A single place where I could see my CI Job history, Unit Testing Jobs and Monitoring/Backup history for all/a subset of my orgs.
I am using Gearset more and more to manage the state of my org's metadata, so it would be nice to be able to see it all in one place.
4 votes -
Need a Lock to the Custom comparison filters
We need a lock to the custom comparison filters so that the team will be on the same page and only the deployment manager can be responsible for all the deployments
3 votes -
Allow adding "No Difference" items to package. To help with package reuse to multiple orgs
Allow assets with "no difference" to be added to a promotion to allow the same package to be used to both promote as well as sync other sandboxes (without having to manually check if asset was changed in each).
33 votes -
Suppress "changed on" datetimes in difference viewer where datetime is the same as the metadata retrieval datetime
The difference viewer will show Changed on values for the current datetime for certain metadata types - probably because SFDC is returning such a value when, in fact, the source didn't change at all
- Custom object
- Settings
- Standard valueset
- Workflow rules
displaying the current datetime of the compare run (i.e. the metadata retrieve datetime) is not helpful when trying to filter on changed date in the difference viewer (i.e. sort descending)
2 votes -
Select all objects in a data deployment
It would be useful to select all objects in the data deploy screen to make it faster to select a large number of objects (even better would be the ability to group objects and select whole groups at once)
5 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 -
Enhance capabilities around 'co-administration'
In our organization we have a couple different salesforce admins that are administrating the salesforce development pipeline in which several developers are making changes and deploying them via gearset. Right now it seems cumbersome/duplicative to do this particularly around the area of adding a sandbox org and then managing permissions of the developers to that sandbox. It would be nice if there was a way for one admin to connect the sandbox, grant the other admin "Owner-level" access to it, and for the two admins to have a shared view of the user access to that org, so I can…
2 votes -
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 vote -
Create a Master-Switch Only deployment process
Can you create a master-switch deployment option? It would be similar to how this operates: https://sfswitch.herokuapp.com/
The issue is that this master switch does not always work with managed packages in production orgs.
So a way to automate the turning off/on of Validation Rules, Process Builders, Flows, and Triggers.
Use Case: We are building a new app and have significant data migration to do. It would help to have a master switch to turn off processes in PROD, deploy date, then, flip the master switch back to turning processes back on.
2 votes -
Offer to push components that passed validation even if some items failed
For large payloads (thousands of artifacts) it can be tedious to try to resolve a few minor issues when 99% of the package will deploy successfully. Having a feature to push stuff that passes validation would be helpful. Included in this in the deployment summary and deployment reports will be a count and list of items that failed validation and were omitted from the package so they can be investigated
9 votes -
Ability to chose multiple targets for a deployment
It would be nice to be able to deploy to multiple environments all at once from one source.
36 votesWe're currently reviewing how we can facilitate deployments to multiple Salesforce instances simultaneously. Please let us know how you manage this currently, or how you would like to manage it - thanks!
-
Default to Object View
Option to default to Object View vs XML for metadata types that have it available
9 votes -
Delete records from the target org during a data deployment
Provide options to delete records from Target Org. This will help clean up of test data and reload from Source.
17 votes -
Allow PMD to be configured by uploading a xml file with rules
We use PMD locally in our IDEs to analyse during development, and the whole team shares a rule file in xml. It excludes the ones we don't like and configures other rules.
We can configure Gearset to do the same through the UI, but I'd rather be able to just upload the file, then I will know they are the same set of rules.
3 votes
- Don't see your idea?