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.
1304 results found
-
Pull Request Branch Filter/restriction
Currently creating a pull request from the "Create pull request Screen" provides the user with a list of all the branches.
The default of this seems to be based on the last location you had selected when you created your branch (This usually ends up being main). As we have a pipeline this is the last place you want anyone being able to create a PR into!
It would be great if we could whitelist/blacklist a bunch of Branch names on this dropdown to stop users accidentally selecting main when creating a PR (for most users this would be one…
2 votes -
package missing -meta.xml endings
When I download a package from a CI Job, it doesn't include the require "-meta.xml" ending for my metadata types. I wrote the following script to add them back one folder at a time. It would make more sense if Gearset just gave me the correct filenames when I download the package though.
…# Gearset gives us a downloadable package to trouble shoot, # but it doesn't have the -meta.xml text appended to it. # Find all files with this ending and append -meta.xml to it. find ./ -type f -name '*.flow' | xargs -I '{}' mv '{}' '{}'-meta.xml find1 vote -
Set Problem Analyzer to default with all rules disabled
Problem Analyzer rules are automatically enforced for CI Deployments which are misleading to end user as the default has ALL rules set to enabled. My recommendations is to have the default template have ALL rules set to disabled OR have clear communication in the CI Deployment feature to notify users that Problem Analyzer rules are enabled and may cause expected deployment behaviour/errors.
3 votes -
disable the ability to delete backups to prevent malicious actors and accidental damage
A lot of backup providers offer the ability to disable the ability to delete backups. This provides protection for 2 scenarios:
A hacker compromises an administrator account and uses this access to remove backups to prevent recovery after ransomware or other attack
An administrator accidentally deletes backups that are required
If there is a legitimate use case for backups to be deleted, the ability to delete can be temporarily turned on but only by contacting support and only with the confirmation of 2 or more admins.
2 votes -
Invoke Run Anonymous Apex against target in CI Job
Team,
Can you please add Run Anonymous Apex option in a CI Job ?Step#1
In this scenario from Developer's end they should add pre scripts in a.txt file and add post scripts in b.txt file in their Source ControlStep#2
How it should work
- It should allow the CI job to run Pre and Post Deployment scripts
- Pre Deployment scripts should be picked up from Source control a.txt file and Post
Deployment scripts should be picked up from Source control b.txt file
- Post commit the diff of commit should identify what are pre and post scripts…6 votes -
Share edit access to a CI job with another user
Currently, only the owner of a CI job is able to edit it. This is a risk, as the owner is not always available to troubleshoot CI issues. It would be helpful to be able to delegate edit access to other team members so that pipelines can be managed collaboratively.
6 votes -
Share edit access to a CI job with another user
Currently, only the owner of a CI job is able to edit it. This is a risk, as the owner is not always available to troubleshoot CI issues. It would be helpful to be able to delegate edit access to other team members so that pipelines can be managed collaboratively.
3 votes -
Run pull request validation against a different sandbox than the one linked to the target org
Hi team,
We have multiple developers creating PRs against a common development branch (let's call it simple, develop; developers are creating their feature branches from master, the Production configuration branch). Develop branch is linked to an integration environment (called INT). INT environment contains multiple stories which are not yet in Production (some of them might go in Production, some will not go).
I would like to get my PRs validated in a Production-copy environment (called BUILDCHK) just to get a real feedback on how "deployable" are my changes in Production, for whenever their time will come.
It would be great…
2 votes -
Add the checks on the PR for the deployment
Currently, gearset doesn't provide the checks on the PR for the deployment CI job. It would be nice to have the checks of the deployment status along with a link to the comparison on the PR, similar to how we can link out to the validation job
2 votes -
Ability to delete app visibility
As per the official reply from Gearset support
".....The issue is, if you manually delete the app, all the app visibilities will be deleted as well. But when using Gearset to delete the app visibilities, they are not completely deleted but set to false. The best workaround for this is to manually delete the xml from your git branch. ..."
If Gearset can incorporate this feature, it would be nice.
The workaround is not that hard as it may sound. 4 apps in 60 profiles takes about 10 mins to mass-find and mass-replace in VS Code.
1 vote -
Add option to "run tests if X is present" on CI jobs
At the moment Gearset only offers an "all or nothing" option ("run all tests"), which is safer but completely ruins minor and cosmetic deployments (because it then takes half an hour to deploy even the smallest, inconsequent change like a Layout change) or "apex or nothing" option ("Default") which does allow for minor deployments to go through.. but also anything that's not Apex, which is dangerous because what if I'm deploying other automations like Flows? these changes would go un-tested.
At the very least an option for "run all tests if Apex OR Flow is present" sounds mandatory. But ideally…
4 votes -
Backup data search feature should allow wildcards
Current the backup/restore search feature is an exact match search only. It would be great to use wild cards or to select "contains" "starts with" "ends with" or simply allow the user to use % to achieve the same.
For example if I wanted to search for the account Willy Wonky Chocolate Factory, with the exact match I have to know the exact name, but with wild card I could search for %Chocolate% and get all accounts backed up with Chocolate in their name.
1 vote -
Allow switching authentication provider (SSO)
I made the mistake of using the wrong SSO provider (Salesforce) on the main user account that owns all the pipelines, CI jobs, credentials, orgs, etc and now I'm stuck with it with no decent way of changing to Google, my preferred provider. Please create an easy way to switch SSO providers.
2 votes -
Include "Messages reported by Salesforce" during Metadata Deployment in the final report
During a metadata deployment, on the "deployment in progress" screen, there is a column for "message reported by salesforce".
I think these should be included in the final results screen, and perhaps in the deployment report.
These can be useful for the user to do things like make changes to their flows to conform to salesforce best practices.
2 votes -
When merging a Pull Request that is linked to an Azure DevOps work item, indicate the user who performed the merge
Currently, when a PR is merged into an Org (and the PR is linked to an Azure DevOps item), a discussion comment is added to the DevOps item documenting the merge. However, there is no indication in the comment to document the user who performed the merge. The Author of the comment appears to be the owner of the pipeline, not the user who performed the merge. My suggestion is to either make the author of the comment the person who performed the merge, OR in the content of the comments, add a line to indicate "Merged By: [Name of…
1 vote -
retain validation history for CI jobs
When a pull request is created against a branch that triggers a CI job, a validation is run. Sometimes, this validation hits errors and adjustments need to be made to the metadata filter and/or problem analyzer template until the validation succeeds. However, once the PR is promoted and the CI job successfully fires, the validation history for that PR is no longer accessible. It would be useful to be able to retain that validation history, as it would help to do further investigation into the validation errors that were hit after the fact.
There is not always time during a…
1 vote -
Provide deployment options for Mulesoft via Gearset
As Gearset does Salesforce based deployments so well, it would be great to have Mule deployments done through Gearset as well.
3 votes -
Include Pull Request title in the notification
Hello GS team,
Currently, the notifications from the pull request validations only include the PR number, I would like to request if it's possible to include the PR title.
Current Sample: [Gearset] CI validation job Validation job for PR #11111 failed
With the title in the subject of the notification, we can FW the results to the right teams automatically.
Thank you!
3 votes -
add a column for file sizes and show a warning message if over the limit (might happen deploying content assets)
Recently when deploying a large amount of content assets, I ran into a issue where the deployment would freeze on caching metadata for faster comparison.
Support told me the deployment size was too large and I broke it up into smaller deployments. I suggest adding a column with file sizes and perhaps a warning message if you exceed the deployment limits.
3 votes -
Allow automated unit test execution to run tests synchronously
When unit tests are run in parallel you can often get intermittent errors such as UNABLETOLOCK_ROW. When running tests from Salesforce you are able to specify running tests synchronously which takes longer but prevents conflicts between tests. Can this option be added to Gearset for the automated test running?
1 vote
- Don't see your idea?