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
-
Retain source control branch selection when cancelling a comparison
If you click "compare now" and then click "cancel" before it finishes, the "compare metadata" screen retains your selection for orgs, but does not retain the branch selection for source control.
It defaults to the first branch by alphabetical order versus what I selected before I cancelled. This can cause confusion for users who do not notice.
1 voteThis has now been implemented and should have the expected behaviour
-
Ability to lockdown access to delete Deployment history
It'd be nice if there was a way for admins to restrict access for devs/other users when it comes to deleting items from deployment history. The use case here is when a sprint is done and we're promoting changes from QA to UAT, it'd be nice to select all the sprint packages and combine them from deployment history so a user doesn't have to go through each change at a time. Providing full access to everyone opens the possibility for them to delete a package that should've been bundled with other packages on the promotion to UAT.
1 vote -
Add a search function to the Monitoring > Unit Tests
Add a search function to the Monitoring > Unit Test page to quickly find a specific Test outcome
1 voteReleased on 07/01/2021
-
Exclude LWC Jest files from validation and deployment
We introduced LWC - Jest tests for our project, which seems to cause validation errors with Gearset.
As per Salesforce recommendations it is recommended to keep jest tests only locally and in VCS and avoid trying to push them to SF as they would cause validation errors.
Is there an forward path that allows us to tell Gearset to exclude LWC - Jest files from validation/deployment?
1 voteThis feature was released on December 1st, 2020. Thank you for the suggestion.
-
ci owner
Allow CI jobs to be reassigned to new owners. Or allow for out of office functionality when CI Owner is out of office.
1 voteCompleted on March 6th, 2020 see documentation on https://docs.gearset.com/en/articles/3758806-transferring-ci-job-ownership
-
Add "Show selected" button to the Custom Filter editor
This button needs to be in the type and items columns. This way the developer will see the already selected components and be able to check faster if everything required is selected
1 vote -
1 vote
This is already supported as a [Named Item] under the [Setting] metadata type. Contact us in the in-app chat if you have trouble locating it.
-
Allow "View Errors" in CI Job History page to be opened in a new tab
It would be great if the button allowed to be opened in a new tab (essentially allow buttons and links to act like regular HTML elements that allow opening in a new tab via Cmd/Ctrl+click or via right click)
Example right clicking the "View Errors" shows no open to open in a new tab https://d.pr/i/m5CNIG
Right clicking "View comparison" allows for it https://d.pr/i/WpCfFF
This is similar to https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/35538631-make-clone-package-openable-in-a-new-tab
1 vote -
Include a Comparison for a Permission Set Group's Muting Permission Set
Include a Comparison for a Permission Set Group's Muting Permission Set. Currently, you can deploy a Permission Set and/or a Permission Set Group. However, if that Permission Set Group contains a muting permission set, Gearset doesn't pull the data. Here is a link to the SF guide on the muting permission set: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_mutingpermissionset.htm?search_text=muting%20permission%20sets
1 voteWe have now added support for this metadata type.
-
Add support for Currency and Percent fields to be masked during a data deployment
We have some custom objects that hold financial data so masking currency and Percent fields will help when doing data deployments
1 vote -
Remove botUser from Einstein Bot metadata
The metadata for EInstein Bots includes a tag called "botUser" that contains the username of the user you've specified to run the bot as. Because it contains a username, the deployment fails unless you have the exact same username in both environments.
My current workaround is to deactivate the bot, remove the running user (which removes the botUser tag), deploy, then reset the changes that I made.
Can we get a problem analyser that will detect and remove this botUser tag so that the deployment will complete?
1 voteHi. We have implemented a PA for this now, which will remove the BotUser field if needed to prevent Gearset from trying to overwrite the user with one from the source.
-
Unique filename of the generated report PDF
Currently, the name of the generated PDF file of the deployment report is always the same for a given source and target.
If we deploy from our "master" gitlab branch to our "production" environment, the name will always be the same.
We archive the report PDFs for documentation / compliance reasons, and we always have to manually rename the PDF file to make the name distinct.
It would be nice if the name of the report PDF was unique. This could be achieved by either including a timestamp or the deployment number into the filename.
1 vote -
Update package.xml with destructive changes which helps CI jobs
When I commit components to bitbucket brach if I have 5 new components and 5 deleted components. then Gearset is updating package.xml in the src folder with only 5 components which are to be created but destructive changes are tracked no where. Then if we deploy from this branch changes to Sandbox using CI job which has 'Filter metadata changes using package.xml' checked, then the deleted components will not be deployed. It is good if Gearset give a feature to track destructive changes and deploy using CI job.
1 voteCompleted on October 29th, 2020
-
Deploy CMS/CRM Connection and and CMS Collections
We would like to be able to deploy CMS/CRM Connection and and CMS Collections. They are a part of Community Workspace.
1 vote -
Documentation around ramifications of deleting a connection (and possibly an Archive option)
I haven't seen anywhere in the support documentation that details any ramifications (if any) when deleting a no longer needed Salesforce connection in GearSet.
The kind of ramifications I'm thinking about are:
Validated Packages based on the connection, could I still review/clone/deploy?
Deployment History - will all information still be available? Can I still clone from a previous deployment?
Comparison History - can I pull up a previous compare?
etc.
If there is any negative impact to the above, then it would be appropriate to have an "Archive" option for Salesforce connections. The thought with this would be one, the…
1 voteHi Jonathan,
I have written a document detailing what happens when a connection is deleted.
You can view it here - https://docs.gearset.com/en/articles/7882840-deleting-an-org-connection.
Thank you for your feedback and please do tell us if there is anything I've missed out.
Quinn Kuiper
Customer Success at Gearset
-
Support the CustomHelpMenuSection metadata item
We use the CustomHelpMenuSection item to customise our Help & Training dropdown list in Salesforce, and we would like to include it in our deployments automatically.
It's been available in the Metadata API since version 45, but Gearset doesn't appear to support it yet.
Will it be available soon?
1 vote -
Add Failure Information to CI Job's Email Notifications
Currently, Unit Test jobs provide a nice email notification of what tests failed right in the email body.
CI jobs, however, provides the same generic message for failures for validations as below:
"The validation only CI job, Release Validation, has failed. Find and fix the validation issues on the error summary page in your CI job history"
and for CI deployments
"A continuous integration job, Prod to Dev3, has failed. No changes were deployed to the target org.
Find and fix the deployment issues on the error summary page in your CI job history. "
It'd be great to get…
1 voteReleased
-
Deployment screen to show which components were selected vs included
When you get to the summary page, often times you will be deploying with the need for sub-components to be included in the package despite them being actual changes.
When you're selecting those items inside the comparison page, it would be helpful to see that total be reflected in the deployment summary page. So if you picked 50 items to deploy but it needed an additional 1,000 components (despite them having No Difference) then we should see those breakdowns on the Deployment Summary
Gearset soft alrt message "Some components with difference type of No difference have been added to the…
1 vote -
Dependency Enhancement for App Menu metadata
Currently, when we compare App Menu metadata, the "Depends On" tree is empty, even though it definitely has dependencies on connectedApps and customApplications.
Please add dependency analysis for App Menu metadata,
1 vote -
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.
- Don't see your idea?