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.
337 results found
-
Add support for incoming webhooks
There's already a way to set up an outgoing webhook after a successful CI job run.
It'd be nice to have a way for a CI job to have an incoming webhook from another service, such as ElectricFlow (a build platform).
One use case would be for CI deployments to be dependent on external validation services.
4 votesThis is now possible since we have released our API, which is available to everyone with an Enterprise license! Please see https://docs.gearset.com/en/articles/6099550-getting-started-with-the-gearset-api for more details. If anyone has feedback or suggestions, please contact us via the in-app widget.
-
Unscramble order of <excludeButtons> tags in Layout metadata
Page Layouts use the <excludeButtons> element to indicate the presence or absence of standard buttons on a layout.
But this element appears in an arbitrary order when retrieved. Unlike other metadata which gets canonicalized by sorting alphabetically.
Gearset could sort these elements to avoid the random order causing random diffs to appear in metadata comparisons when in reality there is no difference.
4 votesWhen Gearset detects that the only differences in your Layout are the result of reordering, and so there aren't any real differences to show you, it will automatically consider this metadata to be unchanged. As a result, this Layout won't appear in the list of changed metadata and will no longer clutter up your comparison results.
If there are any material differences in your Layouts, they will still appear in your comparison results as normal.
And you'll be able to use the Hide reordering checkbox to filter out any immaterial differences, just as you would for other metadata types.
-
There should be an option to schedule unit test jobs weekly in Gearset
Hi Gearset,
I would suggest you to provide an extra option where we can select weekly ,daily or monthly schedule jobs in Unit Testing Jobs.Thank you,
2 votesYou can now choose which days of the week a unit test job should run, allowing you to schedule the job to run weekly.
-
Allow other Enterprise Users who do not own the CI Job to run it
Enterprise Users can only "Run Now" Jobs that they own. If the Source and Destination Org are shared, allow other enterprise users to run the job.
46 votes -
Github Pull Request as a `Draft`
This new feature is great. Would be even better if you can select that the PR be a draft.
1 voteHi,
You’ll now see the option to create a draft pull request in GitHub, if your repository supports draft pull requests.
Draft pull requests are available in public repositories with GitHub Free, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see https://help.github.com/en/articles/about-pull-requests#draft-pull-requests.
-
Include Test Run Details in Deployment Report for Validated packages
In the Validation deployment flow, there currently isn't a way to view test execution results if they aren't manually exported during the process. Having the ability to view the Validation Deployment report and details in this deployment flow is actually more valuable than the actual deployment report that is generated.
If we can't have that, it would be nice to be able to continue to export those test run results after deployment as part of the deployment details.7 votesYou can now access the outcome of test execution results for validated packages via the ‘View components’ menu item located under the More actions icon.
-
Enhance XML meta data comparison to ignore changes in XML order
In org monitoring we frequently get notification about changes an the only thing is a change to the order of the XML elements returned.
The XML is virtually the same but the order of elements returned changed from one day to the other.It makes differentiating "real" changes from those false positives time-consuming.
It would be great if those kind of changes could be ignored or if there was an option to configure the XML comparison behavior for each monitoring job.
15 votesWe’ve made this option available now. See https://docs.gearset.com/en/articles/2413367-why-is-xml-order-of-some-metadata-in-the-comparison-results-different for more information.
-
Migrate audit fields during a data deployment
When deploying data records, it would be helpful if audit fields values could be migrated
7 votesReleased in October 2021 (apologies for the slow update of this post). Users need to enable the "create Audit fields" permission on their org before they do a deployment. Instructions here: https://help.salesforce.com/s/articleView?id=000334139&type=1
-
Include logic operator choices in Data Deployments
Currently Data Deployments only allow filtering on
[FIELD] = [VALUE]It would be beneficial to be able to include other logic operators such as:
NOT EQUALS
LIKE
IN
GREATER THAN
LESS THANetc.
14 votesWe’ve made lots of improvements to the data deployment filters over the past few months.
The filters now include:
- equals
- not equal
- greater than (or equal to) & less than (or equal to) for dates, datetimes and numbers
- is empty & is not empty for nillable fieldsYou can now specify multiple values (use OR logic) when using the equals filter.
We’ve made it easier to input dates and times so that you don’t have to rely on knowing the exact format.
There’s validation so that filters with invalid values aren’t possible. These invalid values would have caused the deployment to fail.
If there’s still further improvements that you need, please could you create (or vote on) a new idea? This will help us identify which improvements are most valuable to you.
Thanks,
Tom -
Gearset API to externally trigger Gearset actions
It would be incredibly helpful to trigger Gearset comparisons, validations, deployments, etc. from an external source using an API. Our team uses GitHub for our VCS, which provides the perfect opportunity to:
1. design webhooks to validate changes in order to approve a Pull Request
2. design webhooks to automatically deploy changes to an org once the PR is approved.Additionally, CI tools such as Jenkins, TravisCI, TeamCity, etc could use such an API to design complex builds that still employ Gearset, but use the external tool for additional actions outside of what Gearset provides for their CI features.
108 votesThis is now available to everyone with an Enterprise license! Please see https://docs.gearset.com/en/articles/6099550-getting-started-with-the-gearset-api for more details. If anyone has feedback or suggestions, please contact us via the in-app widget.
-
Deploy single layoutitems
In Layouts there are multiple layoutItems. it would be helpful if we could to deploy single <layoutItems> from a Layout without affecting other <layoutItems>.
10 votesYou can now deploy single layout Items using Gearset's new Precision deployments feature: https://docs.gearset.com/en/articles/6407322-getting-started-with-precision-layout-deployments
-
Commit-by-commit deployment
As you are giving an option to trigger the CI job based on repository commit, it would make more sense to only compare the source and target based on the commit items and consider the commit changes for deployment based on your selection of either new, modified or deleted and the comparison filter(which can be optional in this case).
This will help in reducing the chances of overriding the changes of other teams working in a shared environment or an environment not in sync with the branch.
There can be other scenarios where we maintain managed package items in the…
43 votesThis was released on the 23/03/2021. Documentation is on https://docs.gearset.com/en/articles/5069914-delta-ci
-
Stamp Deployment Results with Salesforce Id of the Deployment package for auditabilityq
When a deployment is successful, the deployment results/report should include the Id of the deployment package from Salesforce. This would create a foolproof audit trail between Gearset deployments and when they went into effect in Salesforce.
3 votes -
Add the ability to export Success and Error logs for Data Deployments
When I do a deployment it would be useful to download the success and error logs as a csv or excel document
3 votesYou can now download records successfully deployed and any records which failed to deploy due to errors from the data deployment history page (https://app.gearset.com/data-deployment-history).
-
Allow for the masking of data during a Data Deployment
During a data deployment it should be possible to mask the data in specific fields. For example, if I were importing Account and Contact data from production into a sandbox I would want to be able to mask email address so that we can't erroneously send actual customers emails while we're testing
4 votes -
Cloning package should copy over (prepopulate) description as well as friendly name.
I find myself having to go to the original deployed package to copy the description information or coming up with a new description for the cloned package. Would be nice to have this brought over from the original when cloning a package.
17 votes -
Keep the Deployment Friendly Name / Notes when you refresh a comparison
Keep the Deployment Friendly Name / Notes when you refresh a comparison
5 votes -
Ability to deploy remaining Omni-Channel Components
For Omni-Channel deployments, QueueRoutingConfig metadata type is now supported by Gearset. However, corresponding PresenceUserConfigUser and UserServicePresence metadata types are not yet available. This means a secondary Metadata API tool (e.g. ANT, Workbench) or other manual steps are needed to complete an Omni-Channel deployment.
Hoping all supported components for API deployment can be included in diffs for releasing all via Gearset.
5 votes -
Update the CI Jobs Page so you can organize, similar to Deployments History page.
We have a bunch of CI Jobs, and it gets a bit difficult to identify whose job is owned by who just by looking at it.
Maybe make it similar to the Deployment History tab where I can sort out things by clicking the options above like "Owner" or "Name" and it'll organize it the way the Deployment History tab you guys have in place.
2 votes -
Add the open PR feature (Github) to work with BitBucket after a successful commit
It would be great to add the open PR feature (Github) to work with BitBucket after a successful commit.
Super helpful for the admin team to close off their feature branches and move onto the next job at hand without having to interact with BitBucket.
2 votes
- Don't see your idea?