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.
1301 results found
-
Make CI-created scratch orgs more usable by downstream webhooks
If a CI job creates a scratch org ; and you configure an outgoing webhook in the CI configuration, the subscribers to that webhook have no way of being able to connect/authenticate to that scratch org.
The typical use case would be to run automated UX testing (Provar, Selenium)
At present, even the CI job creator can't log into the CI-created scratch org let alone any CI webhook
In addition to supporting this, there should be doc on how a downstream webhook can access the scratch org to then do useful work.
2 votes -
Allow standard linux path in sfdx-project.json
if path contains "./force-app" a bug appears, if we write "force-app" it works. so first one should work to
Repro step :
{
"packageDirectories": [{
"path": "./force-app",
"default": true
}],
"namespace": "",
"sfdcLoginUrl": "https://test.salesforce.com",
"sourceApiVersion": "48.0"
}Result :
Comparision failedExpected Result:
Comparision Ok2 votes -
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 -
Show test apex run in the deployment report
When we validate a deployment then schedule it for deployment. Once deployed we receive a report however the tests run do not show here and you have to back to the validated section to find them - please include the tests run on the final deployment report
3 votes -
Allow outgoing webhook option to be configured for Compare and Deploy
I need the option to configure an outgoing webhook when deploying via 'Compare and Deploy' feature. Currently webhooks are only available with the CI jobs.
3 votes -
mark destructive only changes as a separate difference
due to deployment limitations with salesforce destructive changes destructive changes dont necessarily reflect branch to org so these deltas are being marked as differences even though there is no way to fix other than manually in the org. these should be marked as a separate difference type for easier filtering.
2 votes -
3 votes
-
Be able to log into scratch org from Deployment Success page
It would be super convenient to log into the scratch org directly from the Deployment success page
- From Compare & Deploy sequence
- From CI success
3 votes -
Keep list of specified tests
When choosing specified tests to do a validation, let's say from a comparison that was created from a bunch of drafts that were combined, the pop-up will show the specified tests that were chosen originally for those drafts that were combined. That is awesome and is exactly what I want.
The problem is the "Fetching test classes from Salesforce" then occurs automatically and replaces that list with the full list of test classes, and check the boxes for all of them, replacing my existing list. That means I have to go back and choose my list of specified tests again.
8 votes -
Support for WaveXmd metadata is missing
If we replace default DataSet in Einstein Analytics, it creates another type of metadata "WaveXmd". Support for the deployment of this metadata is missing from Gearset and as per discussion with Gearset team, it's a bug. Could you please fix it.
2 votes -
Show In-Progress Validation jobs when clicking 'Details' in GitHub PR
When viewing a GitHub PR and you have a status check that's in progress, clicking 'Details' should take you to the validation only job page and show all validations (including those in progress).
Currently this page only shows you completed validations which makes it confusing to use at first and you have to navigate to 'Continuous Integration' and find the validation job there.
2 votes -
Allow users to hide or collapse the middle bar of the comparison screen
I have a small laptop monitor, so screen space is pretty valuable to me when working from home. It can be difficult to do code reviews from a laptop monitor because of the middle bar, which takes up a significant amount of real estate.
I rarely use any of the controls or information in that box. It would be great to be able to collapse or hide it to allow more space for the top panel (list of metadata components) and the bottom panel (selected metadata contents)
2 votes -
swapping source and target after compare
I was doing compare between our 2 orgs (Source: UAT, Target: DEVSTG) and I realized that I got the order wrong. Should be (Source: DEVSTG, Target: UAT). But the compare has already completed.
I wish there is a way to just flip (swap) the source and target without re-comparing as it takes some time comparing between orgs.
9 votes -
Display more workflow subcomponents under Workflow for Metadata filter
Currently, two sub-components display under Workflow when selecting metadata types within a filter.
- WorkflowAlert
- WorkflowRule
There's more sub-components than those two and I'd argue that there's two that are frequently used that should be included for visibility
- WorkflowFieldUpdate
- WorkflowOutboundMessage
There's 2 more, but these may be used less frequently and not needed for visibility
- WorkflowKnowledgePublish
- WorkflowTask
2 votes -
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 -
Deploying to an org based on tags
It would be a useful feature to initiate a deployment when a Github tag is created.
1 vote -
Don't Delete Managed Package's object permissions from Permission Sets in CI jobs
In a CI job, using source control as the source and including deleted items, you can run into an issue where objects from managed packages show as "deleted" in terms of custom object permissions from permission sets that have access to them. This can occur for permission sets designed to give access to managed package features or if you have a permission set with "View all data" or a system permission that gives them access to all objects in some capacity (read, write).
Ideally, we wouldn't have to include managed package object permissions into Source Control (likewise, Gearset suggests only…
1 vote
- Don't see your idea?