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.
329 results found
-
Allow date range filtering on the "Changed On" column
Currently one has to pick dates individually, if one has 30 + dates to select, this can be massively simplified if one could select a date range.
14 votes -
How about a default BitBucket repository on the popup page that appears when you clone a package (under “Deployment History”)?
How about a default BitBucket repository on the popup page that appears when you clone a package (under “Deployment History”)?
2 votes -
Allow destructive changes from Local File
Allow for the upload of a local file which includes the destructiveChangePost.xml, destructiveChange.xml, and destructiveChangePre.xml files to do destructive changes.
11 votes -
Include a feature to connect between SonarQube and Gearset
I really love using Gearset. It would be great if we have a plugin in there to integrate Gearset and SonarQube to display Static Code Analysis and Test Coverage in Sonar. I had tried this through CircleCI and it requires lot of configuration and we need write code to create and maintain the connection.
Whenever there is an update to the GIT Master it has to Initialize the Sonar Scanner and it'll run some tests and display results in SonarQube.
Thanks!13 votes -
Use the information in a JIRA ticket to select the components to deploy
Instead of manually selecting components to deploy. If we have an integration with JIRA and the components are listed on the JIRA ticket. Would it be possible to then specify JIRA tickets to deploy and have Gearset automatically build the deployment package?
2 votes -
Enhance the deployment history search functionality
When trying to gather packages together to combine them for a release, currently it is not possible to first limit by a text search then expand the date range (search hangs due to number of retrievals)
Could there be a way to enhance the history search to enable easier searching?
2 votes -
Allow retrying failed validations and deployments
I'm often running into the situation where the validation failed either due to transient circumstances in the org, or due to the org settings being incorrectly configured. In this scenario, I would like to simply retry the validation using the same package, and I'd look for that option somewhere here:
https://app.gearset.com/deployments/validations
Running a new comparison (using the "clone package" option) is unnecessary, takes a lot of time. Also using the "view comparison" option is overkill. I would rather not go through those motions of recalling the comparison results from cache, going through the analysis once again, etc. Because I know…
1 vote -
A configuration to prevent deployment from certain Sandbox Org into Production org
In most of Tech industry deployment lifecycle, all code or config changes are ideally pushed into production only from a FullCopy Sandbox(Commonly Known as Staging Environment).
It would be very good to have a feature in GearSet App which if enabled shouldn't allow user deploying data from Dev/DevPro/Partial Sandbox into Production Org.
28 votes -
Clean up source/destination drop downs to be consistent across all UI elements.
The drop down lists for picking source/destination are different in the UI.
For example, in compare and deploy production salesforce connections are not in the list alphanumerically, they are appended to the bottom while in a clone deployment they are all listed alphanumerically.
Just being picky, but consistency one way or another would be great.
1 vote -
Allow deployment of unlocked packages
At the moment, you can select "Installed package" as a metadata type to compare, and I think you can use this to install a package (without installation key).
However, unless I'm missing them, 2nd Generation Unlocked packages don't appear in a comparison like this.
It would be really useful to be able to deploy 2GP with Gearset because I sometimes need to make metadata changes at the same time as installing
e.g. I'm moving some old functionality into an Unlocked package and that old code has logic in the triggers. I want to be able to delete the old triggers…
16 votes -
Problem analysers - to ignore the user config element
On metadata deployments, I frequently struggle with Report Folders, Workflow Updates, and other configuration elements that have individual users assigned to them. The struggle is that individual users assigned to these config elements often do not exist in the target org. This results in the entire deployment failing, and many times, manually configuring the report, report folder, etc.
A nice solution to this would be a new section on the Problem analysis screen that allows me to exclude the users from the config element that is being deployed.
It is useful to call these scenarios out, because I need to…
1 vote -
Give users the ability to update field/object permissions for specific profiles only
The issue is, when promoting from one org to another and changing either Custom Object Permissions or Custom Field Permissions and if more than the profile you want has been changed, the extra profile changes get promoted anyway. So we need a way to control which profiles get applied when promoting field and object level security.
3 votes -
Need to move Help Menu between orgs
I recently had to move custom Help Menu items between orgs. Since Gearset didn't support it, I was reduced to manually entering the data in each org since they weren't connected in Change Set paths. I believe the metadata is CustomHelpMenuSectio
2 votes -
Create Change set without comparison
Allow user to directly create a change set without doing the comparison. If user has a list of items that needs to be migrated then allow the user to add items and skip comparison step.
25 votes -
Provide an option to run Aura and/or LWC testing before deployment
I don't think that very many people are actually creating Aura/LWC tests yet, but they really should be.
Since SF doesn't require them like it does for Apex, if we decide that those tests ought to be run before deployment, it would be great to have Gearset run them. This will help us to make sure they are run before every deployment instead of relying on developers remembering to do it manually.
5 votes -
Email Notification whenever deployment is successful
it would be good if we can send email notification to Users whenever we successfully deploy components to specific Org regardless of CI job.
0 votes -
Add Upload CSV functionality to create an upload template for CPQ deployments
For CPQ Deployments add an "Upload from CSV" feature where a user could upload a file with specific External IDs across multiple objects to tell Gearset what to migrate in a single click.
For example, the user could list the Object API name in Column A of the sheet and the External ID in column B and then Gearset would parse this and create a Data Deployment based off of those records specifically. This would be incredibly useful for any CPQ deployment where you need to only deploy specific records not the entire object!
8 votes -
Optional ability to provide a warning when targeting a deployment to a Non-Developer Production Instance
I'd love to be able to have an extra "warning" message when targeting certain orgs when clicking the "Deploy" button. The thought is that it provides an extra level of confirmation when targeting production, to help avoid mistakes. This could be an optional custom warning message set on a connection that if populated, a "Deployment Confirmation Message" is shown.
1 vote -
Validation Failures - Show Error in Table
In the new UI for Validation to view failed test classes error messages you must click into each failed class to view the details.
The previous UI showed "part" of the error message within the table. This was extremely useful in identifying all of the "unique" errors that are occurring.
IE: If 58 test classes fail from "4" unique issues -- then in order to determine that you may need to click into all 58 test classes or fix one at a time --> refresh --> validate.
This is just a time save feature.
1 vote -
Show history of changes for a component
When performing forensic analysis regarding how or why something started working differently, it would be a great timesaver to be able to select a component and then be able to select the data comparisons for just that component. For example, select an apex class and then pick date dates so the system can display what changed. I would expect that this would be quicker than going into Monitoring Histories and picking each date and waiting for it to build the entire comparison of everything that changed and then having to find the component of interest.
A follow on to this…
1 vote
- Don't see your idea?