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.
1130 results found
-
Allow deployment of unlocked packages
At the moment, you can select "Installed package" as a metadata type to compare, and I think you can use this to install a package (without installation key).
However, unless I'm missing them, 2nd Generation Unlocked packages don't appear in a comparison like this.
It would be really useful to be able to deploy 2GP with Gearset because I sometimes need to make metadata changes at the same time as installing
e.g. I'm moving some old functionality into an Unlocked package and that old code has logic in the triggers. I want to be able to delete the old triggers…
15 votes -
1 vote
-
Allow destructive changes from Local File
Allow for the upload of a local file which includes the destructiveChangePost.xml, destructiveChange.xml, and destructiveChangePre.xml files to do destructive changes.
10 votes -
Distinguish between code changes and just API metadata changes for Apex in Comparison Window
For large code comparisons, it'd be great to have the ability to see when it's just a change in API vs. actual differences. Right now, you'd have to click on every row to see what the actual change was.
2 votes -
`Deployment history' User Interface update.
In `Deployment history' it would be great if when you choose a target and it opens in a new window. Deploying 48 packages and it is painful.
1 vote -
Allow merging functionality when two branches are compared
right now, when compare/deploying two branches, Gearset only fetches the new changes and creates a whole new separate commit to be pushed to the targeted branch. This causes the targeted branch to lose track of all previous commits from the source branch and when compared in git, it thinks that the targeted branch is still behind. It would be very useful, especially for admins, to be able to use merge compatibility if and only there is no conflict between the two branches.
1 vote -
Webhook trigger when Pull Request is Completed in Azure DevOps
Continuous Integration job to trigger when a Pull Request is Completed in Azure DevOps
2 votes -
Schedule data deployments
The current data deployment functionality works fine for one-off deployments, but if you are trying to keep specific data in sync across multiple orgs, the ability to schedule data deployments for a given time in the future would let you deploy on a recurring basis automatically. Becomes especially helpful when combined with the current data filtering options.
19 votes -
Add a column to indicate if XML matches if order doesn't matter
See this link: https://docs.gearset.com/en/articles/2413367-why-is-xml-order-of-some-metadata-in-the-comparison-results-different
Sometimes, the XML of an item in sandbox/production can be the same, but not in the same order. This leads to false positives showing up in the list as "changed items".
I understand that sometimes order matters (eg: in picklists) but maybe there could be an additional column which shows if there are no differences if you ignore order? Maybe even a setting to turn the column on and off so it's not confusing?
1 vote -
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 -
Ignore sfdx-project.json file in order to compare code using Metadata API structure
I need use the sfdx-project.json file in order to integrate with VS
code, but using Metadata API structure.
Apparently, Gearset is looking for this file to define if is a metadata API or SFDX structure,So I need a ignore looking for this file, in order to compare as metadata API structure.
Thank you.
1 vote -
Allow us to personalize the report generated at the end of the deployment
I want to send the automatic report generated at the end of the deployment to my client. However, I want to personalize it with the logo of my company or add additional text.
5 votes -
Include a feature to connect between SonarQube and Gearset
I really love using Gearset. It would be great if we have a plugin in there to integrate Gearset and SonarQube to display Static Code Analysis and Test Coverage in Sonar. I had tried this through CircleCI and it requires lot of configuration and we need write code to create and maintain the connection.
Whenever there is an update to the GIT Master it has to Initialize the Sonar Scanner and it'll run some tests and display results in SonarQube.
Thanks!10 votes -
Compare and Deploy Attachments and Files
Please add the ability to use the "Compare and Deploy" for Attachments and Files. The ability to migrate PDFs, image files, word docs, and excel spreadsheets would be GREATLY appreciated! Thanks!
19 votes -
4 votes
-
Ability to override custom metadata field settings per org
Our code repository currently contains the custom metadata settings from our development environment. When we deploy to production, we either ignore custom metadata in Gearset and manually add any new custom metadata items to production or we manually select the new custom metadata items in Gearset and then manually update the fields in production from the development settings to the production settings.
It would be great if there was something like the Octopus Deployment tool has where you can define configuration settings for each environment. Gearset would automatically update the field value based on the stored setting for the specific…
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.
6 votes -
track metadata filter changes
Filters are shared by default. However, if someone changes the filter, I cannot tell what has been changed, who made the change or when it was changed. Ideally, I'd like a version history for each filter.
3 votes -
view deployed components live
Show live the components deployed during the running of a CI/CD Job.
Like:
deploying class abc.......
deploying class xyz.......
deploying lightning Component abc.......5 votes
- Don't see your idea?