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.
1250 results found
-
Offer Japan data residency
We are headquartered in Japan. Japan has data residency requirements for data backups/deployments and even metadata deployments/processing.
Please add the option for a Japan hosted Gearset account.
2 votes -
Quick deploy in pipelines
It would nice to be able to use the Quick Deploy feature once a release is validated, instead of either hitting deploy or scheduling the deploy and having it validate one again.
22 votes -
Assigning a dev sandbox to a member should give them deployment access
Assigning a dev sandbox to a member should give them deployment access automatically, or at the very least I should be able to give deployment access in the same interface.
2 votes -
Allow out of order Update deployment
Currently you can only deselect and select update elements in an order. For example I have 3 recent updates ordered 1 to 3. One being the oldest and first update and 3 being the newest and last update. The current functionality would require me to select item 1 if I wanted to also update item 2. And if I wanted to update item 3 I would have to select all the items before it.
I would like to select each one individual no matter there deployment history. Often I need to do this because the updates have no relation to…
2 votes -
give a reminder if I'm leaving out a key piece from my deployment
When deploying a new field, not including any permissions would be strange so a reminder would be great. Think of it as a recipe. If I'm making a pastry and I don't include salt that would be odd so a reminder there would be needed. I might have high blood pressure so there's a reason I don't want to include it but a reminder is helpful. For some deployments its easier to make inferences than others but it's good to starts somewhere.
1 vote -
Download Salesforce customer master data changes for a custom time period in a single file
We get a request from auditors every year. They want to see the customer master data changes for a specific month or time period. The customer master data objects like account, opportunity, contact, lead, etc.
I have a full Salesforce data backup job that runs once per day. If i start downloading the files for each day, it is gonna take a lot of time.
Therefore, I need one export for the whole month for customer master data objects like account, opportunity, contact, lead, etc.
1 vote -
Side-by-side Conflict Resolution for Non-XML File Types
I would like to see the side-by-side conflict resolution that is available for XML files extended to other file types, especially Apex.
1 vote -
Check for maximum flow versions reached as part of the pre deployment error check
The problem analysis does not detect that the deployment will fail due to max number of flow versions
1 vote -
4 votes
-
Compare Types on Comparison
For the pipelines observed when creating a feature branch and during comparison runs, a default filter is applied to the compared types without any metadata types selected (0). We would like to have a custom filter with metadata types for a specific pipeline pre-selected by default when the feature branch initiates the comparison.
3 votes -
Ability to export results of historic test run
When successfully validating a pull request, there is a "view details" link under the "Merge and validation checks" section. When clicked, in the new page that opens there is a button "Export test results…" that allows me to download the test results in excel file with detailed precision, reporting each test method duration.
Unfortunately this feature is only accessible when PR are being validated, and disappears when checking historic PRs already closed and deployed. Would it be possible to provide such data?
1 vote -
Allow customization options for the Deployment Report file name
It would be nice to either have the option to set a default file name or allow the ability to set the report file name in the deployment screen.
For my organization, this would make sorting deployment reports for various projects much easier as the file name doesn't include the Package Label.
2 votes -
Expand Permission reporting on the Monitoring job
Expand Permission reporting on the Monitoring job to include Delete permissions reporting on Objects.
2 votes -
Version Control Commit History in Comparisons
When you compare a version control repo to an environment, it would be awesome to see the commit history get pulled in so you can quickly filter for a specific commit message(s)
0 votes -
Split Lightning Page Metadata Type
Think the Lightning Page metadata type needs to be split into 2 categories. Reason being it is the one metadata type that causes comparisons to run for extremely long times or even crash/time out. This happens because it trying to compare all of the lightning email templates users make. It would be better if lightning email templates were their own metadata type and the lightning page type was actually just lightning pages created for objects.
2 votes -
To provide the deployment history of all deployments, not only the ones from compare and deploy.
It is useful to be able to filter and download all promotion history in a similar way we can do for deployment history.
1 vote -
Write deployment results to a custom Object.
We use a custom ticket object in our processes to track salesforce change requests. The ability to write deployment, validation results to a custom object would be very helpful.
1 vote -
Multiple screens
I work with 2-3 screens. It would be great to be able to split the comparison settings to one screen and have the xml, flow navigator, lightning page visualizer,... on another screen. That way users can see more as they work. As a photographer I use Adobe photoshop and lightroom both applications allow splitting the controls and output.
1 vote -
The Ability to add deployments to a folder or tagging them...
On the Validated packages, Draft Deployments, Depolyment history it would be great if users could create folders or tags to group deployment or validated packages. Use case: Team has a large deployment that will be split into multiple parts a folder or tagging would help with organization and tracking.
1 vote -
The destructiveChangesPost.xml file should be processed in manual comparison
The destructiveChangesPost.xml should be processed when using local file as a source for manual comparison. Ideally the items listed in the destructive file should be used as filter for which to show in the Deleted filter
1 vote
- Don't see your idea?