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.
1422 results found
-
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 -
Delete feature branch ONLY after production deployment
The ability to delete feature branches only after merging with master branch (which runs the ci job to deploy to Production). Currently the feature branch will delete if there is no PR attached with it. There are instances where I may want to delete a PR to the 'QA' or 'Release' branch but still want to keep the feature branch. Currently this is not possible.
6 votes -
View Deployment Summary from Pipelines
My team develops in siloed dev orgs. Once a feature is complete, we create a PR against an integration environment.
This triggers a test suite run in the target org and a peer code review. This process works well for Apex. However, admins on our team build automations in Flow, which are nearly impossible to review in GitHub due to the complexity of the XML.
To address this, we’ve been using Gearset’s Flow Navigator for Flow code reviews. Previously, it only took a couple of clicks to reach the Deployment Summary screen, and the Flow visualization made reviews much easier.
…
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 -
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 -
ClickUp integration would be awesome!
My company uses ClickUp to manage tickets, would be great if there was integration with Gearset as that would save me copy/pasting ticket references into the deployment descriptions.
6 votes -
Incorporate Relationship Graph into metadata deployment
Right now is it not possible to deploy Relationship Graph metadata according to https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_relationshipgraphdefinition.htm with Gearset. This metadata is required for the so called Actionable Relationship Center, which is part of Financial Services Cloud. Even though the meta data is available in the Vlocity filter in Gearset, the items we are looking for doesn't fall under that one. If selected, no meta data get retrieved and therefore no deployment happens.
6 votes -
Add the option to schedule weekly, monthly and yearly backups
To meet our backup compliance requirements I'd like to suggest an option to schedule weekly, monthly, and yearly backups to go along with the daily backup option that is currently available. This way, we could setup multiple backup tasks with different retention.
Thanks
6 votes -
Allow for Scheduled Comparisons
Like Monitoring Jobs, allow users to choose a source, target, and metadata filter, and schedule when a comparison runs.
The primary goal of this would be time savings. To have that data already retrieved and cached so you can go in, make your selections, and move toward deployment more quickly. Possible applications include recurring deployments, planning out your workday, etc. This addition would be for non-Integration users.
6 votes -
In Azure Repositories, maintain owner when changing PR to gs-pipelines
When dealing with Azure Repository, the owner of the gs-pipeline PR is always the user used for authentication. Any way to include the original owner would be helpful since the messaging is lost this way
6 votes -
Allow delegated users to edit environment variables
My user is setup on our CI and I have a number of environment variables setup on Custom Labels for ID's.
Whilst this works great the main issue is if I am Sick/On Holiday there is no way for someone else to go in and add/edit the environment variables thus making me a single point of failure/Reference.
What would be great would be either have Environment Variables setup at a CI level and delegated users have the ability to go in and edit/create new ones against the CI (This would ensure only those that know what they are doing are…
6 votes -
Inline editing of metadata
The idea above was "closed" due to Environment Variables.
That feature is too fiddley for our use case as the change that needs to be performed is not consistent. Furthermore, that feature does not help with handling merges.
Gearset has some merging capabilities, but it only allows to select one file or another, instead of merging changes from both files.
I'm aware it is possible to perform merges from source control, though it would be easier to train our team if they did not have to learn another technology. Furthermore, it leaves the process to more faults as the…
6 votes -
Automate Salesforce org connection on sandbox refresh
When we refresh our sandbox orgs, we have to reconnect the gearset user, would it be possible to use JWT to auto connect to the org?
6 votes -
xml formatting support for Illuminated Cloud
I would like to see support in the 'XML quote escaping style' for Illuminted Cloud (and potentially other IDE Vendors)
I am struggling currently as my Admins use gearset for source control commits and my developers use Webstorm and Illuminated Cloud which causes conflicts (generally with the utf/UTF issues but some others as well around validation rules and some formula fields).
Ideally, If a team standardizes around one IDE then all they have to do is come in to that setting and set it to what the IDE does as a default and then you wouldn't get any conflicts with…6 votes -
Add a 'flag' to ignore XML 'utf' versus 'UTF' in XML header.
I believe there exists a mismatch with the XML header reference to UTF in the Gearset library to what is used in SFDX.
6 votes -
Ability to filter records on field "ischanged" when doing a data backup comparison.
Instead of just being able to filter on field values when comparing a data backup. Give the user the ability to filter on a certain field being changed.
6 votes
- Don't see your idea?