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.
1286 results found
-
Add a batch size option directly on Data Deployment and Data Templates
Currently we can specify the batch size for bulk data loads on Account level.
With this kind of setup we can't have two pararell jobs running on different batch sizes and we also need to memorize what batch size is required for each of my Data Templates.
It would be nice if we could do that directly on Data Deployment job and even save such setting in a Data Template.
1 vote -
'Select All' on Draft Deployments and Deployment History
When combining packages it would be very nice if there was a 'Select All' checkbox.
1 vote -
Jira ticket association should carry over to deployment merges and comparison refreshes
If I clone a deployment, it copies all the associated Jira tickets, but if I merge two deployments, the list of associated Jira tickets is empty. Is that how it is supposed to work? I would expect a union of the lists of all the merged deployments.
The same would apply to comparison refreshes.
1 vote -
WebStoreTemplate
Please add WebStoreTemplate as a metadata type
1 vote -
Jira: Ability to pass a list of Jira ticket Ids vs. single entry
Would really benefit from being able to paste a list of Jira Ids, e.g. comma-delimited (similar to specified tests) on final deployment. Hate giving up validation / deployment status writebacks to Jira, but often we have packages spanning dozens of Jira tickets and entry can be time-consuming, especially if there is a failure or refresh needed and Jira ticket associations get lost from the draft.
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 -
Detailed monitor reports to inbox
Opening the Monitor reports in Gearset is very time consuming. I would like a daily report to arrive in my inbox with the Changed, New or Deleted object names, Data Changed and Who.
1 vote -
Allow invited people to replicate data and metadata from Backup job
Allow the ability to replicate data and metadata for persons with full permissions to a backup job even if they did not create the backup job
With several administrators for a Salesforce organization, the objective with a backup is that in case of an emergency or error it can be fixed within a short period of time to avoid downtime. The backup job allows us to have a copy of our data, but it would also be great if we could have a copy of the person who is responsible for the backup. With just one person being able to…
1 vote -
Ability to trigger different CI jobs or changing the targets based on the user who did the commit in source control
Related to CI jobs can you set up multiple jobs to trigger based on which user did the commit to source control? The goal would be having the deployment / last modified dates in SF reflect which user did the commit in source control and triggered the CI job.
I don't think that's possible as I don't see any kind of filter or way to manage which CI job should fire when source control is updated so the audit history in SF will only reflect one specific user doing the deployments and people would need to review the details in…
1 vote -
Do selective restoration instead of a full restoration.
We want to restore certain fields instead of all data into Salesforce
1 vote -
Add Component's Label and API Name to Export CSV results
Please include columns for the components Label and API Name along with the Item Type and Display Name when exporting to CSV.
Use Case - We use the Export results as a formal Deployment Log that we sharing with a Client's project team. In that log, we include the component's Label, API Name, and metadata Type. Most recipients of this Deployment Log are unfamiliar with the API Name which may not even closely match what the Label is. Having both in this Log would greatly enhance this understanding.
Thanks in advance!
1 vote -
Don't auto-select all tests when choosing "Select which tests to run"
When selecting "Select which tests to run" Gearset shows the tests included in the comparison first, but the moment all other tests are loaded, everything is selected.
When choosing this option, the tests included in the comparison should stay on top and selected, and the rest of the test should be added alphabetically but UNSELECTED.
If I'm choosing this option, I probably only want to run some tests. I think it would be much easier this way. Usually you need to run the tests included in the comparison and maybe one or two more.
1 vote -
Use package xml to populate metadata filter
I suggest to add the ability to upload the package.xml manifest files to populate the metadata filter before the comparison step of an org to git or org to org deployment.
A lot of Salesforce developers use package.xml files locally to deploy some parts of the functionality in order to speed up the deployment process.
Currently, Gearset allows you to select the components via Custom Filters, but it is slow to select about 20 components manually. Uploading the package manifest from the local machine can speed up the process very much,1 vote -
Change Data Capture
When installing a Integration Platform you have to enable the Change Data Capture in order for the platform to receive notifications on changes. At the moment updates under Setup/Integrations/Change Data Capture can not be deployed by Gearset :-(.
1 vote -
Basic Authentication with Jira
As our local hosted Jira instance doesn't allow unnamed connections it would be great to have a basic (username + password) authentication for Jira as well as Bitbucket.
1 vote -
csv export comparison CSV doesn't identify source and targets
When you export a comparison (e.g. selected items), the CSV has column headers for Source and Target. So, someone looking at the CSV can't tell what the source was (org friendly name/repo+branch name) or what the target was (" ")
The file name identifies the source org by xxx@example.com .... but no friendly name which is key when source is a scratch org. No identification of the target at all in the csv file name.
1 vote -
Allow custom endpoints for webhooks from Unit Testing and Monitoring Jobs
You can post to Slack, Teams, and Chatter when an org monitoring job runs. But, as a consultancy, we'd like to post to our own SF org in a more general way. We have records for each of our customers, and it would be good to be able to report on summary data about the Gearset's monitoring for those customers.
If there were a configurable endpoint we could target that at a custom REST endpoint on our Salesforce and then join things up.
1 vote -
Repository Rebasing
Allows the Git repository to be rebased from the latest and greatest metadata from a target organization. In just few clicks the gearset will download all the latest metadata from a target org and will check in it inside master branch
1 vote -
Allow
Once the comparison is completed. Gearset should tell us which commit Id belongs that changes.
Gearset should allow the users to deploy per branch. User will be allowed to cherry pick commit Ids then that commit ids will be package and able to deploy it.
1 vote -
Monitoring enhancement: compare permissions across users
It would be cool if the Gearset Permissions Explorer would help you in determining how to collapse Profiles into fewer numbers. The model would be https://perm-comparator.herokuapp.com/
A typical org has proliferated Profiles over the years, many only slightly different from one another. As SFDC wants us to move to Permission Sets, job one is to collapse the profiles into as few as possible - this requires comparing user permissions against each other (you can't just compare profiles, you need to know what additional permissions some users have vs others too)
Since SFDC is finally making dynamic Lightning pages GA (for…
1 vote
- Don't see your idea?