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.
1139 results found
-
Use triggering branch as source branch in git-sourced CI jobs
Currently:
We have to define a single fixed source branch in a CI job, when it has a Git-Source.Desired:
Option to say "use triggering branch". It should use the branch, where current commit-hook-call comes from.It should allow Pipelines to test also all development branches e.g. with "Validation only" CI-job.
11 votes -
Ability to upload Deployment Checklist instead of manually adding All components
For every release, we have at least 700-1500 or more components to be deployed and adding all those one by one into gearset is a lot of manual effort which might sometimes not be entirely accurate. It would be great if there is an option where we can upload an excel or csv with all the component names and gearset would just create the package for you. It would save a lot of time and effort and reduce manual errors.
11 votes -
Support user record migration from production to sandbox or scratch orgs
New users are often created in the production org that need to be monitored and brought back to sandboxes as well. It would be great if the data deployment tool could support moving user records from prod to sandboxes or scratch orgs.
11 votes -
Support merge fields in outgoing webhooks of CI jobs
When sending an outgoing webhook, I'd like to be able to include if the job succeeded, the name of the job etc.
11 votes -
Ability to add custom trigger points to trigger CI from source control
At the moment the tool allows you to only kick off CI jobs when a branch is updated.
This is actually limiting the capability of the tool in itself,
because services like Bitbucket allows you customize trigger points, as to when they should ping the webhook;
such as the creation of pull request, merging a pull request.The two trigger points mentioned above are specifically very important because you would want to run validation CI jobs on the creation of pull request or when the merge completes so that you can actually ascertain if your branch compiles.
Based on an…
11 votes -
Option to validate / deploy only running test classes in deployment set
When deploying, there's a pain point when we want to specify tests to run. It would be nice to have an option to only run test classes that are included in the deployment. Automatically identifying which test classes are in the deployment package should be fairly straight forward:
grep -ri @IsTest ./src/classes11 votes -
Cancel deployment in progress
In Salesforce, you can cancel a deployment in progress: Maybe because a test has failed already and you don't want to bother running the rest, or because you forgot some things.
Can we have a cancel button while a deployment is in progress in Gearset? The metadata api seems to support it:
https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_canceldeploy.htm
11 votes -
Add "View Validation in Salesforce" to your Github and Teams/Slack Channel messages.
Our pipeline is utilized by some implementation partners that we do not give access to Gearset. They manage their changes that flow through the pipeline with GitHub and receive pipeline updates in a Teams channel. Both of these options have a message to view validation errors in Gearset but the partner teams cannot see Gearset. If these messages included the same "View Validation in Salesforce" option that lives in Gearset, they could be redirected to the Salesforce error page to help their troubleshooting faster.
10 votes -
Show all Github requirements to merge in the Gearset pull request view.
We have required approvals enabled on PRs in Github. Currently when viewing a Pull Request in the Gearset Pipelines view, it does not show that a PR is blocked from being merged because at least one code review approval is needed in Github. This leads to accidentally attempting to "promote" in Gearset and then the Pull Request merge fails. We would like to see these (and any other Github requirements) showing up in Gearset so we are informed which PRs are approved and ready to promote.
10 votes -
Compare Active Version of flows not the newest Flow
When comparing flows please compare the active version of flows, not the newest version. This would align with how change sets handle flow.
Example:
Version 2 and 3 exist in source. Version 2 is active and version 3 is draft. I want to deploy Version 2 that is active not the inactive flow.10 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…
10 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.
10 votes -
Select a set of data deployment templates and run them in order
Ability to build sequence of data load (choose a list of data load templates and have to possibility to run them automatically in sequence). The sequence can be changed.
10 votes -
More granular permission settings for sub groups of a large team
Giving team owners/leaders the ability to define sub groups of team members and control their ability to deploy to certain environments.
For example not being able to connect to/make deployments to 'production' orgs.10 votes -
Throw Error When Invalid Test is Entered
When entering test class names in the text field, invalid entries can be added without any indication that there is something wrong, which would lead to uncovered code and most likely a failed deployment. For example, entering in ThisIsAnInvalidTestName would not result in any error.
10 votes -
Provide ordering for metadata elements when committing to version control
When metadata is retrieved from Salesforce the order of child nodes is not guaranteed and results in false-positive changes when committing to version control. Usually this will be something simple like workflow actions/criteria appearing out-of-order which can be compared manually. However, recently we've noticed entire profiles being committed with every permissions element out-of-order, resulting in a change set with ~20k lines where the actual change is impossible to visualize.
Gearset should provide a feature to 'order' child XML elements alphabetically by name in order to provide consistent commits to version control and eliminate false-positives.
10 votes -
Allow destructive changes from Local File
Allow for the upload of a local file which includes the destructiveChangePost.xml, destructiveChange.xml, and destructiveChangePre.xml files to do destructive changes.
10 votes -
Include a feature to connect between SonarQube and Gearset
I really love using Gearset. It would be great if we have a plugin in there to integrate Gearset and SonarQube to display Static Code Analysis and Test Coverage in Sonar. I had tried this through CircleCI and it requires lot of configuration and we need write code to create and maintain the connection.
Whenever there is an update to the GIT Master it has to Initialize the Sonar Scanner and it'll run some tests and display results in SonarQube.
Thanks!10 votes -
Allow complex filters and child relationships on filters for data loading
Allow complex filters and child relationships on filters for data loading. For example, filter the Account to only load if the Owner is an Active user in the system.
10 votes -
Allow Monitoring Jobs on Source Code Repositories
Currently, Enterprise users can create monitoring jobs on sandboxes, so that they may be notified when a sandbox's metadata changes. It'd be great to be able to perform the same monitoring action against source code repositories (GitHub!).
An example use case would be detecting when undesired metadata types enter into the repository. This is important because CI jobs will fail on certain metadata types, so we want to ensure that they never make it into source to begin with. Additionally, our business has decided that some metadata types should never be captured into source.
10 votes
- Don't see your idea?