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.
1428 results found
-
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 -
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 -
Don't allow duplicate fields in comparison.
If I have a field with name example category. Somehow the same field has been added to the object xml file it needs to throw an error at the time of comparison.
1 vote -
Static Code Analysis for JavaScript Components
It would be great if Gearset could run static code analysis on JavaScript as well as Apex when deploying Lightning Components.
7 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. (this would be something like grep -e 'this' -e 'that')
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…
1 vote -
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 -
Add support for migrating Vlocity Datapacks
Datapacks / Vlocity Metadata
2 votes -
Allow filtering by Deployment Stage/Metadata Subset during comparison
This Gearset article describes some very logical phases for performing a large deployment:
https://docs.gearset.com/metadata-deployment-guides/splitting-a-complex-deployment-into-stagesIt would be nice if there were built-in comparisons to show each subset of metadata.
For example if you were on phase 1 of the deployment you could filter your comparison to just "Data Tier" and Gearset would pre-filter the relevant metadata.
1 vote -
Add functionality to select the changes in the component for the deployment.
I think it will be very helpful to have a possibility to deploy only some selected changes in the modified component.
1 vote -
create an option to have chained deployments
create an option to have chained deployments so complex deployments can be broken down and sequentially deployed or slaves can be ran
allowing for multi staged deployments under one CI job
46 votes -
Allow date range filtering on the "Changed On" column
Currently one has to pick dates individually, if one has 30 + dates to select, this can be massively simplified if one could select a date range.
14 votes -
Badge
To have he possibility to have badge that could be added to the readme of a git repo. Display in green if the test classes have been successful, red if error.
The same kind of badge could be used for deployment.1 vote -
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 -
Attach pdf items details in the email notif "Your organization has changed"
When you receive a notification concerning a change into an organization you need to know quickly which items are changed.
4 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 -
Only display active branches when displaying branches from a bit bucket cloud repository
Only display active branches when displaying branches from a bit bucket cloud repository
5 votes -
Allow CI deployment notifications to the specific user who made the source control commit that prompted the deployment
We have CI jobs that fire on commits to a source control repository. At the moment, there is no way to email the specific individual who made the commit that prompted the deployment, so we have to notify everyone involved in the project whenever a deployment fails. If we could just notify the individual who made the commit (plus the deployment manager), it would reduce noise considerably.
Please add this feature.
13 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
- Don't see your idea?