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.
1138 results found
-
Mark items as already reviewed earlier
Today we are gearing up for a major deploy so we are deploying many different changes into gitHub. It would be nice to be able to mark whole sections of content as already reviewed such that any new comparison could ignore all of that content. Then we could look at only the new or newly changed/deleted content.
2 votes -
2 votes
-
Allow reauthorization of git/Bitbucket tokens used by CI jobs
Currently, if the OAuth tokens used for a Bitbucket integration are refreshed, any existing CI job will not adopt the newly authorized token. In fact, there is no way to even edit the job to use the new credentials; the job must be completely deleted and created anew.
However, in the case of Salesforce OAuth tokens, Gearset already has a Reauthorize button, along with facilities for re-associating the new credentials with saved orgs and saved CI jobs. Please enable similar reauthorization mecahnics and credential saving for other Oauth integrations, especially Bitbucket Server, so that CI jobs will not need to…
2 votes -
Allow the use of cached metadata during comparisons
Over the past 2 days we ran multiple comparisons between salesforce orgs. Nothing was changed in the target org but some fixes were applied to the source org in order to make the deployment successful. A lot of time would be saved if we had the option to compare the source org to a cached copy of the target org. In this case, the source org was finishing very fast, especially when we used the local file comparison.
2 votes -
Add an option to disable deploying the email to case settings in Case.settings
This will allow to deploy Case.settings without getting this deploy error:
EmailToCaseRoutingAddress[Info]: emailServicesAddress is a read only field and cannot be changed2 votes -
Allow for selecting/unselecting Filter by Package.xml
When doing a clone or a refresh comparison today the ability does not exist to add or remove the option of whether you are filtering by package.xml. I would like to see this added.
For us what might occur at times is that we have a release occur where this is accidentally selected and we find that a number of items are missing and due to this being selected. We have no way to remove the selection and have ended up starting over. One of a number of scenarios where it would be nice to have the option to do…
2 votes -
Warn the user of unsaved changes to an org compare filter
It would be nice if we got a warning if we have selected specific components in a filter but havent saved the filter when we hit OK. I've lost a lot of work on a custom filter because I forgot to hit 'Save' - I would have thought it would auto-save when you hit OK.
2 votes -
Allow optional parameters to the GearSet login url to support login method and custom domains if needed
When using Salesforce logins along with a custom domain, the current gearset login process requires 6 steps:
- go to https://gearset.com/
- Click "Log in" in upper right
- On the "Welcome back screen", click "Salesforce (Production, Developer)"
- On the Salesforce Login page, click "Use Custom Domain"
- Enter "customdomain" and click "Continue"
- Enter Salesforce Production Username and Password
If the GearSet login URL (from step 2) https://app.gearset.com allowed for optional parameters, a couple of the above steps could be eliminated
An example URL might be:
https://app.gearset.com?loginMethod=sfProdDev&customDomain=customDomain
or
Then that URL with the params could be saved as a favorite or placed in…
2 votes -
If we move Jira ticket to status "Deploy" -> get the code from the repo ->deploy to destination ORG
For example after Jira status "Deploy" is captured doing a comparison and deploying the changes will work.
2 votes -
Import list of metadata items into org comparison.
When running a comparison, a user should be able to import a list of metadata items based on an agreed format (likely API names). This list would allow the user to save effort from copy pasting api names if they track their changes in an external system. For example, we track changes in our release system within our Salesforce production org. Our manifest items are tracked such as "customobjectc.customfield__c" and have statuses such as new/updated/deleted so we have a historical references of our changes. Being able to import these changes while still having the ability to select…
2 votes -
This is related to webhooks feature in Gearset.
Currently webhooks allow to trigger external job like jenkins job using webhooks. However its doesn't give any information related to this job whether its been called or not or pass or fail.
Use case:
The Jenkins job which I am triggering through Gearset calls my regression tests which runs on Jenkins server. I want to see the information like the Jenkins job has been called successfully and test results like number of tests run, pass , failed etc.
Having this I can make sure the Webhook is working fine and know my test results in Gearset itself.
It would be…2 votes -
Metdata Optimization / CleanUp Analysis
A very good feature for metadata management tool like gearset will be an helper which allow to identify metadata not used or not properly configured.
For example this concurent have this feature : https://www.metazoa.com/snapshot-use-cases-org-cleanup-and-optimization/2 votes -
Combine multiple daily monitoring results into a single deployment
If you want to deploy the differences of an org on a weekly basis, it would be a great option to take the monitoring results of the last 7 days into a single deployment.
Especially in huge orgs, where comparism takes 30 minutes time to show up, this would ease deployment pretty much.2 votes -
Allow sfdx project files for scratch org creation
When creating a scratch org, allow us to select/configure a sfdx-project.json. This will allow for more complicated sfdx project to be deployed, i.e. multiple project folders, namespaces, ... etc.
2 votes -
Allow record id as the first criteria for matching lookup fields
When deploying data records from production to sandbox, the default matching criteria for the owner field will not typically work...
Gearset currently matches on email and profile, but the email addresses for users get modified in sandboxes. So, no match is found for users other than the one who created the sandbox.
It would be great if the first check was: does the user record id match. If not, use email + profile, if not, use the current user.
2 votes -
Add support for migrating Vlocity Datapacks
Datapacks / Vlocity Metadata
2 votes -
How about a default BitBucket repository on the popup page that appears when you clone a package (under “Deployment History”)?
How about a default BitBucket repository on the popup page that appears when you clone a package (under “Deployment History”)?
2 votes -
display meta data filter used on deployment report
It would be useful to see the meta data filter used on the deployment successful report
2 votes -
Allow run tests not only by specific name but by regex
We have a lot of tests and it takes about 2 hours to run them all. But we also have some small services almost completely isolated and which have a specific test class name convention. Currently, we're using ant to specify which exactly we want to run on these services build, so we don't have to wait for 2 hours to deploy a small fix to an isolated service.
2 votes -
Use the information in a JIRA ticket to select the components to deploy
Instead of manually selecting components to deploy. If we have an integration with JIRA and the components are listed on the JIRA ticket. Would it be possible to then specify JIRA tickets to deploy and have Gearset automatically build the deployment package?
2 votes
- Don't see your idea?