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.
337 results found
-
Ability to activate / deactivate Flows / Processes as part of the meta data and/or data deployment process
It should be possible to have gearset to deactivate flows and/or processes based on a selection. And to roll-back afterwards. Similar to what has been created here: https://sfswitch.herokuapp.com/
10 votesHi, thank you for voting on this UserVoice.
Flows can now be deactivated in Gearset alongside validation rules and triggers before data deployments.
Click the View and disable rules... button in the bottom-right of the pre-deployment summary page (next to DEPLOY DATA) to prepare a special metadata comparison.
To deactivate a flow, simply select & deploy its corresponding flow definition.
https://docs.gearset.com/en/articles/4536761-disabling-validation-rules-triggers-and-flows
-
Default option for the deployment component list for JIRA issues
I really like the feature to add a deployment component list to a JIRA ticket. I would like to have the ability to default this ON.
It is currently defaulted to OFF.1 voteWe’ve made this stick to the last deployment on the release of March 19th, 2021. This is per team basis.
-
CI Job notification email should report the actual errors directly instead of linking to CI Dashboard.
This potentially can help the team to collaborate on the errors directly on Teams messages.
For example, at present, the MS team notification says [A continuous integration validation job failed for validation job for PR # xx], but doesn't say which CI job name or what the validation/deployment error was.
1 voteCompleted on 11/03/2021
-
Validation job ownership should be transferred
Good to have capabilities to transfer ownership of validation job to other member in the team so as if one person is on vacation then there should be easy way to transfer ownership of validation job to other member so as if required - Adjustment can be done to CI jobs.
1 vote -
Retain source control branch selection when cancelling a comparison
If you click "compare now" and then click "cancel" before it finishes, the "compare metadata" screen retains your selection for orgs, but does not retain the branch selection for source control.
It defaults to the first branch by alphabetical order versus what I selected before I cancelled. This can cause confusion for users who do not notice.
1 voteThis has now been implemented and should have the expected behaviour
-
Ability to lockdown access to delete Deployment history
It'd be nice if there was a way for admins to restrict access for devs/other users when it comes to deleting items from deployment history. The use case here is when a sprint is done and we're promoting changes from QA to UAT, it'd be nice to select all the sprint packages and combine them from deployment history so a user doesn't have to go through each change at a time. Providing full access to everyone opens the possibility for them to delete a package that should've been bundled with other packages on the promotion to UAT.
1 vote -
Add a search function to the Monitoring > Unit Tests
Add a search function to the Monitoring > Unit Test page to quickly find a specific Test outcome
1 voteReleased on 07/01/2021
-
Exclude LWC Jest files from validation and deployment
We introduced LWC - Jest tests for our project, which seems to cause validation errors with Gearset.
As per Salesforce recommendations it is recommended to keep jest tests only locally and in VCS and avoid trying to push them to SF as they would cause validation errors.
Is there an forward path that allows us to tell Gearset to exclude LWC - Jest files from validation/deployment?
1 voteThis feature was released on December 1st, 2020. Thank you for the suggestion.
-
ci owner
Allow CI jobs to be reassigned to new owners. Or allow for out of office functionality when CI Owner is out of office.
1 voteCompleted on March 6th, 2020 see documentation on https://docs.gearset.com/en/articles/3758806-transferring-ci-job-ownership
-
Change default sort order of Saved Comparison Pairs to use 'Friendly Name' (or last used sort column)
The new Saved Comparison Pairs feature is great! However, the page appears to load connections in a seemingly 'random' order on each use.
Confirmed with Gearset Support the default sort order is by create date of each connection pair. However, if feature is used with multiple connection pairs spanning multiple individual instances this requires manual re-sorting of connections every time page is loaded if you want to view pairs logically by naming convention (e.g. Alpha 1->2, Alpha 2->3, Bravo 1-> 2 , Bravo 2 -> 3 etc.) or something other than system create date.
2 votesSorting by “Last used” column has now been fixed.
-
Include more details in webhook notifications
It would be great if webhook would include, at least, the same information as email notifications. For example, Unit Testing job notifications via email contains the details about the unit tests that failed; however, webhook notification don't. We wanted to use webhooks to get notifications in MS Teams but without the same details, it's not that useful.
2 votes -
Restore/export certain fields on objects
We (the user) would like to be able to restore data, but only select certain fields to be restored.
Usecase:
A business user triggers some automation that modifies a field or specific fields on a large number of records that should not have been modified. In the meantime, other fields may have been modified that were correctly modified. We would want to restore a set of records from a specific backup, but only the specific fields that should not have been modified.5 votesYou can now select which fields you would like to restore, via the "Restore changed fields within <object name>". Example in the attached image.
-
Add "Show selected" button to the Custom Filter editor
This button needs to be in the type and items columns. This way the developer will see the already selected components and be able to check faster if everything required is selected
1 vote -
Option to group and show all selected items while creating new custom filters
Option to group and show all selected items while creating new custom filters
5 votesFilters > Selected Only option was release in the custom metadata filter on the 27 Oct 2020
-
1 vote
This is already supported as a [Named Item] under the [Setting] metadata type. Contact us in the in-app chat if you have trouble locating it.
-
Bitbucket pull request add Default Reviewers
When using the "Create Pull Request" link on the deployment screen, please add the "Default Reviewers" to the BitBucket pull request.
Currently we have to edit each pull request and add the reviewers manually.
5 votesThis has been released on October 1st 2021
-
New Analyzer to prevent endpointURL changes for Outbound Messages in Sandboxes
A major pain point and blocker to use automated CI jobs is that we cannot include workflow rules because we have outbound messages set up to specific test endpoints per sandbox/environment. As the workflow metadata type allows us no ability to filter by workflow rule name (it's by object), this means we have no option but to manually run the comparison and deployments for each of our sandboxes.
It'd be great to add a problem analyzer to suggest not changing the endpointURL field on outbound messages when the target is a Sandbox. This way, you can deselect it manually when…
3 votes -
Add ability to Ignore Warnings to avoid treating Salesforce warnings as errors
See IgnoreWarnings parameter: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy.htm
6 votesWe have implemented this feature now. To toggle the setting, navigate to My Account (using the dropdown next to the Gearset logo), then Salesforce deployment.
-
Select the fields to deploy during a data deployment
Hi we use the data deployment feature is it possible to only select some fields to deploy data from one org to another and not always all the fields on an object.
19 votesYou can now select fields to exclude during a data deployment
-
Allow "View Errors" in CI Job History page to be opened in a new tab
It would be great if the button allowed to be opened in a new tab (essentially allow buttons and links to act like regular HTML elements that allow opening in a new tab via Cmd/Ctrl+click or via right click)
Example right clicking the "View Errors" shows no open to open in a new tab https://d.pr/i/m5CNIG
Right clicking "View comparison" allows for it https://d.pr/i/WpCfFF
This is similar to https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/35538631-make-clone-package-openable-in-a-new-tab
1 vote
- Don't see your idea?