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.
1240 results found
-
Please add support for decomposeCustomLabelsBeta
Salesforce added the option to configure multiple features in the DX Project Configuration file. One of the is breaking down the big CustomLabels file into individual files where we no longer need to deploy the whole file but just a file (label) that has changes in. Please see SFDX Documentation here - https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_ws_config.htm
11 votes -
Remove "No Difference" items when commenting on jira tickets
when i connect a jira ticket to a commit, I like the way gearset posts a comment on the jira ticket listing the changed items. what I dont like is the long list of "no difference" items posted on the ticket. It makes the ticket comments super long and annoying to scroll through. can gearset update this to only post the difference metadatas, or at least give us the option to include or exclude
4 votes -
Add "Open Branches" Tab to Development Sandbox Environments in Pipeline
The only way to deploy an existing feature branch into a development sandbox is to perform a manual compare and deploy. Previously, we had our developer sandboxes set up as static environments which allowed us to create PRs against them for "re-deploy". This is not possible with the new Development Sandbox format. I suggest another tab be added called "Open Branches" which will allow the developers to select a feature to pull and work on in their development environment. That way we get the benefit of easy compare & deploy instead of having to manually compare and deploy. This will…
4 votes -
Precision Deployments for Flow
Please add Flow for Precision Deployment. The new flow visualization has been really great and it would be very helpful to be able to use precision deployments with them.
17 votes -
It would be great to have a centralized way to view all components and static code analysis results for every commit within a branch.
It would be great to have a centralized view for all components and static code analysis results across every commit within a feature branch. For example, if a developer makes five commits to the same branch, it would be much more efficient to review the components and static code analysis results for the entire branch in one place, rather than checking each commit individually through the deployment history. Additionally, there should be an export option to easily share the results with developers. Thanks
3 votes -
Provide the ability to get a deployment report on multiple deployment packages
Instead of having to download the deployment report individually for multiple deployments, I would like to be able to select multiple deployments and download one report that contains a list of all files that were deployed as part of the multiple deployments. It is too cumbersome to manually download a report or .csv for each deployment and then copy/paste the info into one location so that I can get a comprehensive list of all files that were deployed.
8 votes -
Allow users to choose their default comparison view
Different types of Gearset user will prefer to analyse comparisons in different ways. Some will definitely prefer the XML view; others will prefer the new simplified views.
I think it would be great if Gearset allowed users to specify their default view and comparisons load with this preference.
3 votes -
Clickable Jira Request within Pipeline Promotion History
I would like the ability within the pipeline promotion history to make the Jira tickets clickable. That way a user could simply click the ticket reference to navigate directly to the request.
1 vote -
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…4 votes -
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 -
jira comment after deployment
Right now gearset posts comments to Jira when validation is completed and PR is merged.
We would like to have comments also when deployment is completed.The current comment "Successfully merged PR #297 from gs-pipeline/SF-23601-preprod into preprod" tells nothing to business users, they are not aware of git, CI/CD and what this message means.
Comment "Deployment to preprod is completed" makes much more sense for them.4 votes -
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 the ability to put CI jobs into folders
It would be great if we had the ability to put ci jobs into folders. We've accumulated a number of CI jobs. Some of these jobs are no longer in service and we're a bit reluctant to delete them as they may have historical information that we may later want or need. It would be great to be able to put things like this into folders to help reduce clutter and organize our CI jobs page. thanks for your consideration.
4 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 -
sidebar
Love the comparison v2 but can there be an option to collapse the side bar with all the metadata types? When doing diffs sometimes I wish I could have the full width of the screen.
2 votes -
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 -
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
- Don't see your idea?