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.
1354 results found
-
Bash scripting
Add support for bash scripting. This is one of the most powerful features of Jenkins and something that would make a huge difference in Gearset.
7 votes -
Add Validate pull requests for custom git
We have self-Manged Gitlab as a git provider.
It would be good to have the possibility to allow to run validations on pull requests for custom git repositories orsupport on-prem GitLab (submitted as https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/39728857-add-validate-pull-requests-for-on-prem-gitlab)
7 votes -
Better error reporting when CI jobs fail.
Better error reporting when CI jobs fail. Many times I open a failed job and there are no errors reported.
7 votes -
Namespace Mapping for Managed Packages
We are an ISV partner with a managed package we sell to lots of customers. That means our package is namespaced. However with a distributed development team and multiple dev orgs, all source code is not namespaced, and is maintained in source control (github) without namespaces. Only upon unit test and promotion to the package org, does the namespace get added. This results in two basic problems (and others). 1) comparisons between unit test and package result in almost everything being flagged as "changed" due to the namespace, and 2) all aura components are always flagged as "new" when they…
7 votes -
Static Code Analysis for JavaScript Components
It would be great if Gearset could run static code analysis on JavaScript as well as Apex when deploying Lightning Components.
7 votes -
Automated User Test Suite Integration
Such as Selenium and/or Cypress.io
7 votes -
Save previously entered comparison filters
I am currently using a standard regex filter each time I do a comparison. It has become quite lengthy such that I can't easily remember it. I have ended up saving it in a separate text file and have to open it, then copy and paste it into Gearset each time I do a comparison. Pretty cumbersome.
It would be nice if the Filter... text box on the comparison results screen was a combo box that when clicked, dropped down a list of recently used filters. Each entry in the list should be removable (like with a little 'x' icon…
7 votes -
Chatter posting to
I think it would be useful if Gearset had the capability to make a chatter post to a specific group or @mention someone.
7 votes -
Provide a way to init a sandbox
It would be nice if there was a quick way of init'ing a new sandbox that matches either what was in source control or an existing sandbox.
Currently, I need to run a comparison between the existing source and the new sandbox and then I can try the deploy, but it would be nice if the compare step was not needed and I could simply say 'overwrite what is in the sandbox with what is in the specified source'
7 votes -
Differentiate XML and Code differences in the comparison
I would find it very useful if the comparison result highlighted if the difference was in the XML or the Code (or both) for each item. This would especially save time when there are a lot of differences.
7 votesThanks for the suggestion Celio.
We think this should be possible to do and are doing some background work into how to manage and display this. More details to come soon.
Thanks,
Jason. -
Specify tests to run on the test monitoring jobs
Some of my orgs have many tests, and I don't always want to run all of them on a daily basis. Being able to specify which tests are run daily would be great.
7 votes -
Add ability to exclude specific files/folders of repo from a compare with source control
Currently, if you try to compare a repository to a Salesforce org, it will throw an error with only the ability to send a report to Gearset if the repository contains files that are not compatible (gulp files, package.json, etc. at the root of the repo or any folder that isn't corresponding to a Salesforce type of file).
My suggestion would be to add the ability for the user to exclude those files or folders from the compare and retry when it fails. This issue currently prevents us to use source control in the comparisons.
7 votes -
Ability to Select and Merge Specific Changes in Lightning Components and Flows
We are using Gearset to compare and merge changes in Lightning and Aura components, as well as Salesforce Flows. While the tool works well overall, we’ve noticed that it currently lacks the ability to select and move specific changes during a merge. Instead, it requires replacing the entire file, which isn’t ideal in many cases.
It would be extremely helpful if Gearset could allow selective merging of specific lines or sections—similar to how it works for Apex classes. This feature would greatly improve control and efficiency when working with Flows and Lightning components.
Thanks for considering this enhancement!
6 votes -
Save Problem Analyzer Changes to Deployment Set
When using the Problem Analyzer to identify and fix issues within deployment sets, it's common to add or remove items to address specific problems. Currently, these changes are not automatically saved, which can lead to recurring issues in subsequent analyses.
Suggested Enhancement:
Introduce an option that allows users to save their modifications directly to the existing deployment set or create a copy of the set with these changes. This feature would streamline the problem-solving process and ensure that resolved issues do not reappear in future analyses.Benefits:
Efficiency: Reduce the time spent on re-analyzing and re-fixing recurring issues.
Consistency: Ensure…6 votes -
Automate Jira Status when a Pull Request is created in Pipelines
Presently, the capability to automatically update the Jira Status of a ticket is limited to transitions occurring between different environments in Pipelines. Enhancing this functionality to include automated updates triggered by the creation of a Pull Request would prove beneficial, eliminating the need for manual intervention when transitioning to stages such as "Code Review."
6 votes -
Delete feature branches in Github in a way that they can be restored
I closed a PR to master, and Gearset deleted the feature branch. However, it wasn't merged, so I wanted to restore it to continue work. I was completely gone from Github. I believe Gearset should do a normal delete that allows restoration instead of completely obliterating feature branches or allow an option to do so.
6 votes -
Enable us to customize the Slack notifications from Gearset
Enable us to customize the Slack notifications from Gearset (e.g. add deployment Friendly name to Slack deployment notifications). Thanks
6 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 -
Expand the options for "Run job" times on the continuous integration job setup.
Currently the "Run job" option has times for 1, 2, 4 and 24 hours. With international teams working on projects, it would be nice to allow for something like every 8 hours. That could either be a new set option in the list, or allow for a "custom" option. If the pipelines can handle between 1 and 24 hours, let us selection "custom" and input the hours for the job interval to run.
6 votes
- Don't see your idea?