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.
1317 results found
-
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 -
Allow capability of excluding IP ranges from Profiles during migration
Currently IP ranges defined in, say, a sandbox get carried over to the target environment (another sandbox or Production), when Profiles are migrated.
In some cases this means, these means these IP ranges may have to be manually removed from the target environment.
It would be great, if there were an option to exclude these IP ranges from the selected Profiles.1 vote -
Allow Source to choose multiple Branch for CICD Validate/Deploy
when choosing source as GitHub it allows user to choose feature/*** which allows every commit on branch name starts feature will trigger the CICD
2 votes -
More granular permission settings for sub groups of a large team
Giving team owners/leaders the ability to define sub groups of team members and control their ability to deploy to certain environments.
For example not being able to connect to/make deployments to 'production' orgs.10 votes -
OAuth support for outgoing webhooks
Currently outgoing webhooks support only basic authentication. It'd be useful to have oAuth support for outgoing webhooks for enhanced security.
5 votes -
Sort Deployment Details by New, Changed, Deleted
Currently, it seems that the list of Deployment Details provided in Successful Deployment reports is sorted alphabetically by metadata type.
It would be easier to understand the impact of the deployment if the list was sorted first by category (Changed, New, Deleted, No Difference) and then secondly by metadata type within each category.
1 vote -
Control in which country data backups are stored or alternatively export backups automatically..
We require the ability to control where our data is stored. At the moment we need our Swiss backup data to be stored on Swiss servers. If this isn't possible it would be great if we can automatically export data via an API endpoint to our Swiss server.
1 vote -
Add the ability to restrict the Jira Projects Gearset can access
A Jira account may be linked to many projects which will never be interacted with through Gearset. However those projects might still be legitimate for the user, so they can change their project access on the Jira side. It would be great if we could select projects in the connection that we want to choose from when associating to a Jira item.
1 vote -
To be able to filter within a dropdown
https://ej2.syncfusion.com/vue/documentation/drop-down-list/filtering/
Much like the above, when searching through many fields it can be tedious1 vote
- Don't see your idea?