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.
1405 results found
-
Inline Editing of metadata
Inline Editing of metadata
In order to make our deployment successful we had to download the package, modify the version numbers on the flow definitions, and then compare the local package to the target org. It would be very helpful if we can edit the metadata XML in the UI so we can fix the version numbers.110 votesHello. A large number of commenters requested the ability to carry out value replacements as part of metadata deployments.
Gearset now offers a feature called Environment Variables that lets you do just that!
It works with both manual and CI deployments and lets you target either a Salesforce org or a Git repo of your choice. And, for a number of key metadata types, you can even specify the exact 'field' where the replacement should take place.
If you have any feedback on the Environment Variables feature, please open a new feature request or simply let us know in the in-app chat.
Thank you for upvoting this feature request and we hope that you will find the Environment Variables feature useful.
Blog post: https://gearset.com/blog/environment-variables/
Support doc: https://docs.gearset.com/en/articles/5557015-using-environment-variables-in-gearset
-
Ability to use Sandbox Source Tracking features as opposed to a comparison filter
The comparison screen is great to help admins and declarative users see the changes they made. However, it still requires them to know which metadata to pull based on changes they made.
Source tracking in Sandboxes is in beta and would alleviate this concern.
https://help.salesforce.com/articleView?id=sfdx_setup_enable_source_tracking_sandboxes.htm&type=5
If Gearset could leverage this functionality (potentially leveraging SourceMember object or storing .jsons to track last modified times as local projects store) it would make the complete process easy to use for all alike (pull metadata, select diff, deploy).
5 votesWe’re currently working on a technical spike to incorporate source tracking capabilities into how we retrieve metadata. We’ll keep you updated on progress.
Regards,
The Gearset Team
-
Automatically identify and run unit tests for deployed classes
When deploying, we have standard options for running tests. It would be great, if we have an option for "auto-specified tests" where Gearset would automatically find test classes for classed being deployed.
It can be done that in Setup, the team will define what type of extension the test classes has and then Gearset would use that key to find matching test classes.
E.g. we have the class "AccountServices" and we have developed a standard set that the test class has extension "Test", so "AccountServicesTest". In the Gearset setup we would set the variable for tests to "Test".1 vote -
Create a persistent default setting for Monitoring Job Notifications
It would be nice if there was a way to default the notification for monitoring jobs to 'send notification only when changed'. Right now, if you set monitoring, you get an email a day from that job, regardless if there was a change or not. You have to manually change it otherwise.
Nice to have that setting front and center, available when you select monitoring, as well as have a default value for each org type; Prod, Sand, and Dev.
2 votes -
Custom ordering option for CI Dashboard
Rather than splitting jobs into Validate and Deploy and ordering alphabetically, allow custom ordering (drag and drop, or custom grouping) in order to maintain logical job sequences including a mix of deploy and validate jobs.
3 votes -
Display Deployment Status Progress
In the past in Gearset, you were able to see the status of your deployment (e.g. 100/200 test classes, etc.) very similar to how you would see the native status tracker on the Deployment Status page within Salesforce Setup. It appears this feature is no longer available in Gearset and there is no status until the deployment complete. It would be great to bring this back to Gearset, so the tool provides the full deployment scope. Since this has been removed, I now have to open an additional page to monitor progress in Salesforce.
10 votes -
Launch into our Connected Organizations from various screens in Gearset tooling.
Since we have orgs setup in the Monitoring Dashboard or simply in the list of Organizations under My Connections can we get a button that can open that org in a different browser tab ... it would be a super usefuil feature for those of us monitoring many many orgs. its like SFDX ORG : OPEN -u alias name .,..... but having that ability in the GS Tools in relevant areas ... (Monitoring, or My Connections come to mind first.) We have a mixture of DEV, Production and other scratch orgs both internal and External Clients ..... its not always…
1 vote -
Individual Assignment ruleEntry
Please Allow us to Deploy individual Assignment ruleEntry rather than the whole file/set, similar to components in other objects, sharing rules.
1 vote -
Delegate access to a scratch org
The ability to delegate access to a scratch org without extending access to the related production environment would be helpful. We have situations where we need developers to build new ideas in a scratch org but do not want to extend the access to the production environment
1 vote -
Problem Analyzers don't evaluate changes made from other Problem Analzyers
Even though this example has an easy workaround, it does seem like a scenario which could present issues in other deployments.
In the scenario where a standard application that doesn't exist in the target (ex. Sandboxes and LightningInstrumentation) is included in a deployment (along with its permissions), there's 2 problem analyzers that come into play
"Remove standard application additions/deletions from deployment"
"Remove items which reference the listed components which are not available in the target"
When both metadata types are selected (application and permission) only #1 is flagged. This means Gearset removes the standardApplication, but leaves the references to the…
2 votes -
Provide Salesforce error message for Backup Failed Jobs
For Data Backup Jobs that fail it would be beneficial for the corresponding email to contain the Salesforce error message that caused the error.
Or at the very least provide the error in the user interface of the failed Data Backup Job on Gearset site.
1 vote -
1 vote
-
Create post deployment automations to SF records
Hi Gearset😍
Love your deployment product!We are using salesforce as a ticketing system - any chance you are planning to make a connection to Salesforce records like you did for Jira or Azure?
I would love the have the option to do some things automatically after a deployment, for example:
Attaching the deployment report to the ticket
Updating Status field
Update Environment Field (based on target org name)
Posting a chatter post about the deploymentThanks!
1 vote -
Clone deployment package from within the CI job history
We have a feature branch we create a PR 1 to SIT -> we merge the branch -> deploys to SIT -> we delete the branch
We have a feature branch we create a PR 2 to SIT -> we merge the branch -> deploys to SIT -> we delete the branch
now both PRs are in SIT branch
we make a PR from SIT to UAT -> Both PR's are validated against UAT -> if all is good both PR's get deployed to UAT
but then Monday comes and business wants JUST PR1 to be deployed to production
so…1 vote -
Lessen Permissions Needed To Run Monitor
When running Monitor, a user needs to have "Modify All Data" or "Modify Metadata Through Metadata API" permissions, and "Author Apex" is further needed if we want to monitor Apex classes. I understand why an user would need these when comparing for a deployment, but for a more "read-only" use case like running Monitor, is it possible to lessen the permissions needed?
Context: we're looking into using Gearset for auditing purposes, and the Monitor feature looks to fit our needs; that said, if in order to monitor production changes requires the user to have full deployment permissions (and author apex),…
1 vote -
Add Apex Page Permissions to Repo Dependency Cleaner Functionality
It seems based on the below doc
https://docs.gearset.com/en/articles/3624846-what-does-gearset-s-repo-dependency-cleaner-do
That the repo cleaner will remove permission references related to the following deleted items:
Apex Classes
Tabs
Apps
Object Permissions
Field PermissionsMissing from that list is Apex Pages. It'd be great to have that included to clean up references to the deleted page without having to re-run a 2nd comparison for source control.
1 vote -
Allow custom manipulations to data during a data deployment
Export the selected data source in a CSV file before deploying, in order to allow custom manipulation. Then allow the import of that CSV to destination - functioning like a more sophisticated Data loader.
3 votes -
Allow searching Monitoring of a system by a specific record of metadata to see all the dates that the record changed
If I need to find when a specific thing was changed in our system, my only option is either to use the last edited date or to manually check every daily comparison from Monitoring to see if it changed. Since many metadata types do not reliably update the last edited date, it makes it much harder to find those changes. If I could choose a specific metadata record and use that to search the Monitoring to see when it changed, it would be much easier to find it.
10 votes -
Exclude specific Classes from Scheduled Unit Tests
Some Testclasses only run successfully, when the Org is connected to a Backend Application. Usually sandboxes for Development are not connected to the Backend. These are the Orgs, that we need to watch. It would be useful to exclude specific Classes on specified Environments from being tested in scheduled Unit Tests.
10 votes -
Control When Tests are Ran Based on Metadata type
It would be nice to control when we want tests to run based on the type of changes in the triggering event for CI. Something like only run test classes on update of Apex Classes, Flows, Workflows, and Objects.
This is a bit of a patch for not having test classes fully optimized but would be helpful with orgs who have lots of profile and layout changes.3 votes
- Don't see your idea?