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.
1251 results found
-
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…5 votes -
Integrate with Continue https://docs.continue.dev/
My org already pays for Continue as an alternate to GitLab Co-Pilot
1 vote -
custom meta data filtering based on its value
Currently Custom Meta data records cannot be filtered based on what value they hold. This is a critical item, as we have several custom meta datatype record that would require to be filtered based on the value of a particular field in the record.
1 vote -
Customize the columns in the Compare and Deploy view, such as replacing 'Changed By' with 'Created By
Currently we cannot modify or customize the columns in the list view. So if I wish to see the records having created by instead of last modified by then there is no direct option available on UI at 'Compare and deploy'. It is really useful to have the choice over choosing the right columns as per the deployment needs.
1 vote -
Option to create a CI job only for back propagation
We created some CI jobs for back propagation of changes from Production to other downstream branches and orgs. But these CI jobs also pick up pull requests(from a different pipeline) for forward propagation.
So, basically there is no way currently to create a CI job just for back propagation. It will be good to have a toggle in the CI job to mark it for forward or backward propagation9 votes -
Share a deployment with a different team
If I use my Gearset instance to deploy for a client, I wanted to share the deployment history visibility with the client's Gearset team.
1 vote -
Allow for CSV to be extracted data type from completed deployment screen
Allow for CSV to be extracted data type from the completed deployment screen
1 vote -
Add Salesforce Data Cloud sandboxes as an option for deployments
Salesforce Data Cloud sandboxes are now generally available but to promote changes from sandbox to production, the only options are through Data Kit and change sets, CLI, or DevOps Center. Having the option to use GearSet would be helpful so all deployments were managed the same.
2 votes -
ability to clone the 'Deployment Pipeline' and edit the connections as per new project requirement
Every time a new project is kicked off , we need to setup the same pipeline with different org and bitbucket connection, gearset should have ability to clone the complete deployment pipeline so that only connections or branches needs to be updated for quick setup. Also some time the owner of the Deployment pipeline needs to be changed so this feature will give ability to clone the pipeline and disable the old pipeline.
1 vote -
View Locations Not Covered from test results
In the Salesforce's deployment result metadata there is details -> runTestResult -> failures -> code coverage -> Apex Class Name -> locationsNotCovered.
It would be very useful to be able to see the locations not covered of any apex class in the test results section of the UI.1 vote -
Re-introduce last used comparison filter
When I start a comparison, it used to default the filter to the most recently used filter. But now it always shows as "On-Demand Comparison". Can you please restore the previous feature...it's easy to overlook that the correct filter isn't shown and you can waste time doing a comparison against the wrong filter. Adam from your team confirms "Yea that was introduced when we overhauled our comparison tool, you'll need to switch to the filter you want to use each time."
1 vote -
precision deployment for Record types
precision deployment for Record types is required. currently when i try to deploy a record type gearset automatically adds all the picklist fields in that object. if we wanted to deploy only record type or only selected picklist fields currently its not possible. hence, precision deployment is needed for deploying record types
2 votes -
Fix Report/Dashboard Compares to honor RegEx "Include" on folder names (don't return ALL report folders)
Currently, if using regex to include only certain patterns for reports and dashboards, the regex works properly for the reports and dashboards returned, however, it has NO effect on the folder names. The Compare should ONLY return the folder names that match the same regex expressions if there are only include regex'es - it should remove folder names that do not exist in the regex expressions.
1 vote -
Add a Button to Retry Validation on Updates
The new Updates feature is great, but there isn't a "retry" button when there are validation errors to resolve. It's not very intuitive to have to cancel the update and go start over to retry after fixing validation errors. Currently it just shows that the validation failed and the update can be cancelled. It isn't clear what to do after resolving the validation error, and a retry validation button would simplify the process.
I had an error related to a manual change that needed to be enabled in my sandbox, and I had to cancel the update to get it…2 votes -
Allow configuration of where pull request/merge updates are posted in Jira. User comments are being missed because of the volume of updates.
Allow configuration of where pull request/merge updates are posted in Jira. User comments are being missed because of the volume of updates from Gearset when moving a set of changes through the pipeline. These updates are important and we want to keep them, however having the ability of moving them to another tab/section on the Jira ticket would mean we could keep the comments section for user comments only.
2 votes -
Removing an Updates Sandbox from the pipeline should close all associated PRs and branches
I noticed that deleting a sandbox with outstanding updates from the pipeline does not close any associated PRs. These and their branches should be removed from source control automatically. The branches are especially problematic as the GUIDs make it extremely difficult to associate them to an environment and determine if they are no longer needed.
1 vote -
documentation
I have been really impressed by the visualizations on the Compare and Deploy interface. Particularly the lightning page layouts and flows. One of my most time consuming tasks is creating internal documentation and I have not found a tool that allows me to capture the level of detail that I want in an efficient way. It would be great if I could export the visualizations at the bottom of the compare and deploy screen. It would be even better if it could export directly to Confluence.
2 votes -
Automatic sandbox updates option
The new sandbox updates process is really convenient - you can see all the updates a sandbox needs and apply one or more. However it is still very much a manual process to start it. We have a team of engineers and each one of them has to constantly go and trigger the update process manually whenever an update becomes available.
It would be really nice if there was a switch for 'Automatic updates' i.e. whenever it is turned on, the updates are applied automatically during off hours.
Of course if an update fails the engineer would receive an email…
2 votes -
Add regex or other means to "exclude" strings in monitoring job
The Wave dashboards have a key field that changes every day and causes false positives in the Monitoring jobs. I would like the ability to exclude that string pattern from the results so I don't have a bunch of changes that don't matter showing up every day. Regex seems like the most robust way of defining it.
1 vote -
Allow configuring Unit Test jobs to run without code coverage
Ideally I would like to track code coverage, however due to an issue we're having with Salesforce, it's taking 12-24+ hours to run all local tests, crippling our ability to run unit tests nightly. I've discovered that when turning off code coverage when initiating test runs via the tooling API, test runs take significantly less time. We have been working with Salesforce support on this, but as a workaround it would be very useful for us to turn off code coverage for Unit Testing jobs.
2 votes
- Don't see your idea?