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.
1140 results found
-
Modify files during deployment process
In Salesforce, if you add an image to a PathAssistant, it hard codes the sandbox URL in the metadata. This causes failures when you then try to deploy that item to the next environment. My idea is that a feature is added that would allow some sort of find/replace logic that's applied prior to the CI compare. Something like:
File: Enter the name of the package file
Search Text: The text and/or regex string to search the file for
Replacement Text: The text to replace found the text withIn this way, it would modify the source file prior to…
2 votes -
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 -
Allow bulk export of selected objects in selected historical data backups
It would be great to export all, or a selected timeframe, of data backups for a job. I understand this would be a large volume of data so selecting by object would be great.
For example, if there is a data backup for all objects that runs daily, I'd like to select the Account object and select a backup timeframe of 1/1/2020 - 12/31/2020 to export a .zip folder of 365 Account.csv files.
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 -
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 -
SFDX projects and source format and CLI useage
Gearset CI only supports SFDX source that follows the SFDX project template structure (e.g. force-app/main/default/classes and so on). However, SFX CLI doesn't mandate that structure.
SFDX allows you to group metadata by function or logical group (so you can combine metadata in any way that makes sense to you) . We have many projects like this that gearset cannot deploy.2 votes -
Checkboxes to delete multiple packages/validations/deployments at a time
Hi - feature request:
Checkboxes on the validated packages (and probably others) screen so that I can delete validated packages more quickly. One by one is a big pain, and it probably uses your storage... and it definitely clutters our workspace.
Thanks!2 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 -
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 -
Add capability to export components as part of the full deployment history export
It would be good if we were able to export the individual components that were part of a deployment when we export, say, the full deployment history from the past 6 months, or all time.
This would help with IT audits.2 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 -
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 -
Add additional controls to Monitor
Hello Gearset,
We are exploring using the "Monitoring" functionality to audit our Salesforce production metadata changes for our IT Controls. It looked promising until we found out that anyone on the team can edit any monitor job setting, which creates a loophole in the controls that we can't monitor the monitor.
So I'm curious to learn from Gearset whether any of the following can be done/requested:
* Can we limit the Monitor jobs to only be editable by the person who created it?
* Can we show either an audit history or LastModifedBy/LastModifiedTime of the Monitor job?
* If the…4 votes -
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 -
Gearset should control the order of deployment for Report Types, Reports and Dashboards
Dashboards require Reports, and Reports require Report Types. Yet when I attempt to deploy a group of components that comprises all of the necessary components, I'm hit with errors that the required components don't exist <yet>. That shouldn't happen. This is going to <artificially> require me to do multiple deployments. :(
3 votes -
add the ability to filter Git repos on connection
It would be useful to be able to select only applicable Git repos from source control that will interact with Gearset. A user may have many repos that they need on their account, but of those there may only be 1 which would be used via GearSet. It would be great if we could select which repos should be available when setting up the connection to our source control (specifically I am requesting GitHub but I think this would be useful for all source control integrations).
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 -
Display Permission Set changes as one entry
When working with Permission Set changes, it sometimes would be useful to see them grouped by Permission Set instead of being disaggregated by field. For example, we are migrating from using Profiles to Permission sets to grant all access. Currently, if we make changes to many (>100) fields in two different Permission Sets, we have to review many (>100) entries. Also, grouping by permission set would allow us to deploy changes to one Permission Set while ignoring the other.
2 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
- Don't see your idea?