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.
1235 results found
-
Friendly name should be surfaced on the deployment summary page.
The Friendly Name should be surfaced on the deployment summary page, either as a row in the "Summary" section or in its own section, similar to Deployment Notes.
We often track deployments by saving links to the deployment summary. But there is not an easy way to grab the friendly name if we want to search the deployment report; for example to combine packages.
4 votes -
Run only apex test thats related to the Pull request for Validate pull requests targeting the source branch
When we check Validate pull requests targeting the source branch for the Pull request , it runs all the test class irrespective of the package content that being pushed.
It should not run any test class if pushed metadata is only configuration.
It should run only test class if pushed metadata ha class.1 vote -
Add ability to disable all comments on JIRA tickets
Currently, when adding a ticket number in JIRA connector on a deployment, there is no possibility to disable comments sending on JIRA.
This can be a problem, as JIRA tickets can also be seen by our final users, and this "XXX has deployed the ticket" kind of comments can question them.
3 votes -
Ability to Export SFDC Fields into a CSV File
Would it be possible to get a feature where we can download the fields into a csv file?
1 vote -
Use external script/template for masking data
I would love to be able to use my own script/template when doing just data (not having the compliance option) to select what fields I want to mask and the format for how I want to mask them. I will explain more.
When doing a data deployment (data seeding) to our developer sandboxes, I would like to be able to use an external script/template for masking data. In my script/template would like to be able to set the format for the masking and how much of the value to mask. For instance maybe I want to mask a phone number…
2 votes -
Show data hosting option chosen for an account
It would be great to see the chosen data hosting option for an account in the 'My Account' area. Without it security audits will not be able to verify what setting was chosen and will have to rely on documentation held elsewhere.
1 vote -
Allow exporting of custom filter settings
I have some regexes configured specifically for continuous integration, changing these would likely break our CI process. I would like to be able to export a JSON or YAML (or whatever sensible text based format) of my filter configuration, so I can easily view which metadata I'm selecting and excluding through regex, and possibly commit this file to source control.
This is primarily because our team shares filters, and I'd hate to lose the configuration because of someone mucking up.
3 votes -
Re-validate a deployment after failure without returning to compare
Would love the ability to re-validate a deployment after making changes to the target org. I notice this a lot if there's a username issue that needs fixed in the target, I'm able to fix the issue without refreshing the comparison, but still have to return to the compare, go through the automated fixes, and then re-validate the deployment.
2 votes -
CI Job History - Show what CI runs were manual and who triggered the manual run
It's nice that the CI job history shows the source commit link for the auto triggered deployments from Github merges, but for visibility and transparency it would also be good for users to see when a job was triggered from a manual run and what users ran it.
4 votes -
Empty cache during meta deployment process
Before you deploy but after you start the process it should be possible to refresh / empty cache to make sure that any updates to the meta data in either source or target are updated.
3 votes -
Limit Connections creation
Currently there is no feature to prevent users in creating their own connections within Gearset.
We need users to follow the permission that was setup on the shared connection. We have only 2 users that have the approval to deploy code from a sandbox to production. As they can set up their own connections then this bypasses our restriction
Having a permission only available to the Enterprise user or a user approved to create connections and delegate access would prevent the bypass of access permissions
3 votes -
Allow for cross-object mapping with the data deployment add-on
It would be so powerful to allow users to map data to different objects using the data deployment tool. It would allow us to move data efficiently between orgs that don't have completely aligned object APIs and metadata.
3 votes -
Last Modified in Metadata Filter
It would be great if I could set a "last modified" filter when setting which metadata to pull. Rather than go to Apex Classes, wait for the list to refresh, then cherry-pick them, it would be great to simply compare Apex classes modified today, or in the last 30 days, or in the last hour, etc.
4 votes -
Support for WaveRecipe metadata is missing
There is no support for Wave Recipes currently and we are not able to deploy dashboards via Gearset and Continuous Integration.
4 votes -
Option to retry Deployment after failure
Currently, if your deployment fails you have two options:
- Click "back to results"
- Click "new comparison"
Going with option 1 means it needs to re-load the comparison and then click next and re-run all the analyzers again which can take a varying amount of time depending on the size of the comparison/deployment.
In situations where the deployment failed, but the fix is to change something in the org manually - it'd be great to have an option to simply "retry deployment" from the failed deployment screen and skip the various screens and re-loading.
3 votes -
Improve error message when XML is not properly escaped
When I choose to compare metadata with my source as my VCS, there was an "&" char in the recordtype XML definition file.
<values> <fullName>Food & Beverage</fullName> <default>false</default> </values>This threw an error and there was no support and no explanation at that time.
I suggest you to improve this error message.
Message I got:Could not parse the XML for 'force-app/main/default/objects/Lead/businessProcesses/Buyer.recordType-meta.xml'. Error occurred at line 71. Further details: An error occurred while parsing EntityName. Line 71, position 29.
File, line and position it's ok. maybe a link to Gearset docs with walkthrough with this probable cause when a parsing…
1 vote -
Delete comparisons
Be able to delete a comparison run with wrong filters or just keep the latest comparison
1 vote -
Ability to choose whether or not to respect the forceignore file
Would like a checkbox on the comparison screen that allows me to choose whether or not the comparison will respect the contents of the forceignore file. (Similar to the checkbox allowing you to choose whether or not the comparison should use the package.xml file).
Our usage of Gearset does not align with our usage of the forceignore file for automated deployments. In fact, we often use Gearset to manually compare and/or deploy items that we specifically ignore for automated deployments.
Summary of problem this new feature has introduced:
We use gearset for org -> git deployments, and for git ->…5 votes -
Add Salesforce ID to Export History button
Can you add the Salesforce ID to the Export History button for reconciliation purpose.
We currently have to manually match the Salesforce ID in Gearset with the Salesforce ID on the Salesforce Deployment Status page to get the reference between the source ticket in Jira and the deployed change for compliance purpose which is a time consuming process.2 votes -
To give the option to export , Class wise test coverage report in some Excel format
To give the option to export , Class wise test coverage report in some Excel format
3 votes
- Don't see your idea?