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.
1309 results found
-
Add Provar integration for testing to support companies that already have investment in Provar.
Integrate Provar for testing.
3 votes -
Metadata filter - ability to select Report/Dashboard folders by parent folder name
When setting up a metadata filter for a new comparison, when it comes to Reports and Dashboards, it would save sooooo much time if they could be selected according to the top-level/parent folder that they reside in. That would enable the ability select all reports within a single parent folder at once, rather than having to select reports separately which reside in a nested/child folder.
3 votes -
Monthly sandbox refresh from production
I would like the ability to refresh a sandbox from production on a scheduled recurring basis on a monthly cycle (ex: from prod to a full sandbox) so as not to overwrite current development items that are in process or testing.
3 votes -
Ability to change Formula Fields to other Field Types
Gearset doesn't help with one of the most common deployment headaches: changing a formula field to a non-formula field type. It's still a nightmare even with Gearset.
What would be awesome would be if you had a "Change Field Type Wizard" where we could say FormulaField1 needs to become TextField1 and it would do multiple deployments to accomplish the changeover:
- get components
- deploy temp field of new type AND update all existing components to reference the temp field instead of the formula field
- deploy delete of formula field
- deploy text field in place of the old…3 votes -
call webhook with scheduled deployment
We would like Gearset to call a webhook when a scheduled deployment completes. The message to the webhook should pass a message with the org name, UTC datetime, the deployment friendly name, URL of Gearset deployment results and a status field with 'succeeded' or 'failed'
3 votes -
Provide integration with WebexTeams
We moved from Slack to WebexTeams and have lost the ability to post deployment notifications from Gearset. Here's an article about Webex Bots: https://developer.webex.com/docs/bots.
3 votes -
Find/Replace before deployment
Allow a basic find/replace to run against files before final deployment.
Examples: a username that would work in the sandbox that does not exist in production and we need to change it. Or deploying to a packaging org required a modification due to various namespace issues. Other tools have a means to do this in one way or another.3 votes -
Clone Package - keep Tests list
It would be great if when cloning a deployment, it can keep the tests which got performed in the original deployment. Right now, we need to keep a list of the tests which ran on a doc on the side.
3 votes -
Deploy data from local repository.
It would be very helpful if we could deploy data from a local repository. We have different namespaces for internal packages and it would make data migration significantly easier if we could do it from a local machine where we'd switch the namespaces.
3 votes -
Ability to tell what metadata filter someone used in a compare/deployment
For compliance, troubleshooting, and collaboration purposes it would be great to see what metadata filter a user used on their comparison
3 votes -
Remove the "run as specific user" completely from the dashboard prior to deployment (set the options to "Run as
Add during problem analysis:
Remove the "run as specific user" completely from the dashboard prior to deployment (set the options to "Run as logged-in user"). Deploy, then change it back to whatever you need. Based on https://developer.salesforce.com/forums/?id=906F0000000DCJPIA4
3 votes -
Deploy SOAP APIs like Permissionset assignment
I am able to deploy profile components and permission sets separately. But the permission set assignment is part of salesforce SOAP API and I couldn't deploy the same using GearSet.
Kindly provide deployment options not only for Metadata API, also SOAP APIs3 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…
3 votes -
Ability to update value of Reference field for a data deployment
"Select reference fields to deploy"
Ability to edit the value for the target deployment data for the reference field instead of searching for the match on the Target.
Ex. Loading Opportunities from a Source to a Target that contains 5 different record types, but when uploaded to the Target we specify the recordtypeid to one that matches a recordtypeid on the Target for the entire data load.
Similar to how the Owner reference can ignore the Target's users and default to the running user of the data deployment.
3 votes -
Ability to have Tests to Run during Validation to default to Unchecked all
Ability to have Tests to Run during Validation to default to Unchecked all vs all checked (even before they finish loading into the component). We often validate with only a few tests or predefined group of test classes that we input into 'Specify Tests to run' and if a user inputs those test classes in the text area before all the Tests populate above in the list, it will include all of the ones available. It defaults to checked all and they need to remember to uncheck them or to wait for them all to load which can take awhile…
3 votes -
Make it easier to select all custom field translations for deployment
Right now if you want to select translations for certain custom fields, it is necessary to expand the sub-components for each field and select the translation. The second option is to go to the custom object and expand the sub-components in order to check translations which will include all the custom field translations for this object.
It would be helpful to get a way to select the translations for specific custom fields in the deployment.3 votes -
Create a way to apply a regex to all currently selected metadata types when building a filter
The regex support you currently have doesn't really allow for complex (multi-match) regex matching, which is probably ok
If I select, say 116 of the 124 metadata types identified, and then have to apply a regex pattern to each one, it gets pretty tedious. Click-paste-apply 116 times, and then 116 again for the other half of the complex match. I'd write a tool to automate configuring a filter in gearset. :)
If I "select all" then deselect the 8 types i don't want, and THEN apply a regex to all types, that would be pretty great.
3 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.
3 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.
3 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
3 votes
- Don't see your idea?