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.
1244 results found
-
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.3 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).
2 votes -
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 -
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 -
To add capability to mark (to ignore) not selected items to be able to remember that the particular item is not required to be deployed
When compare source and target, sometimes u do an educated decision to NOT select something, and then selecting the rest of the items. Then if the compare results saved as a Draft Deployment, u may return back to it, and do a refresh for the comparison. In this case Gearset would kindly save all of the selected items. But for items that were not selected by the user, not they are mixed up with the new differences. So user have to remember, that this particular item he did not select intentinally, but this item that is not selected is a…
11 votes -
Connection List Search Feature
Add a Search feature to Connections Page. I have 59 connections at the moment and the only differentiation between them is a suffix at the end of the login. It would be nice to be able to quickly search the list of Connections like a CTRL + F would do.
I often have to scroll the list and compare login usernames.
2 votes -
Allow Package Version Mismatch Bypass for Org Deployments
When deploying a branch to a Salesforce org where there is a managed package version mismatch in the file metadata, it would be nice to be able to bypass this discrepancy as there are occasions where there may be a newer package version in a lower/sandbox org and an older package version in a higher/production org.
11 votes -
Set values on record creation for fields that can't be updated
Some objects, for example PriceBook Entry, must have their attributes set on insert as once created most of the record is not updatable, e.g. CurrencyISOCode cannot be changed on this record once it has been inserted. Providing a way to set these fields on creation, rather than a later update step, would allow these records to be deployed as currently PriceBook Entry records fail in multi-currency orgs as they are all created with the default currency causing SF to treat them as duplicates
2 votes -
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 -
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 -
1 vote
- Don't see your idea?