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.
293 results found
-
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 -
Remind repo owner to upgrade metadata on SFDC version change
Your blog post https://gearset.com/blog/mdapi-versioning-and-version-control says it all under the paragraph labeled "Upgradingyour repository's metadata"
But there's no real reminder to tell the team that this is a meritorious idea. My suggestion is that for the first 30 days after PROD is updated, you could display (in color) some alert (or maybe introduce a messages feature) wherein you tell the team that the repo's package.xml is out of date (version wise) with PROD version and provide pointers on how to upgrade, including nuances like Flows (v44).
It is too easy to get lazy and leave the repo metadata out of date…
1 vote -
Enable Defaults or Recently Used on Clone Deployment Page
When you clone a deployment package you have to select your Source details, but the selections do not default to the the last used settings or to a recently/commonly used settings. This is a minor annoyance but in other parts of GS you have the last selected options already selected based on user history, so hoping you can extend this to the Clone page
1 vote -
Export snapshot of production org to git
I'd like to be able to export a snapshot of all the metadata from my production org (include all components) to my git repository by clicking a single button.
After every release, it's worth taking whole metadata export from the org to git for the next/on-going releases.
For now, we have to create a couple of metadata projects to export the metadata to git, which is a tedious job and takes a lot of time.
1 vote -
create a visualization of the DevOps process
Creating a visualization of the DevOps process removes the need for separate Visio diagrams or visual aids to represent the process. Also by creating this feature, you could allow for a drag and drop type feeling to represent CI Jobs, Data Deployments, Comparisons, etc. Users who may be new to a DevOps environment would pick up the process quicker allowing them to quickly adapt to the tools and this type of deployment mentality.
2 votes -
Target Process Integration
Agile/sprint planning tool similar to JIRA
1 vote -
Show Created By and Created Date when doing comparisons
When looking at a comparison it shows changed by as a column, would be helpful for consultants to Show Created By and Created Date as well
6 votes -
Ability to set a friendly name to the package
Should it be possible to set an equivalent of "friendly name" in Gearset but one that can also be spread to Saleforfce.
1 vote -
Add system log fields for created and updated operations for filters
It will be helpful if we know who/when a filter is changed. And it would be great if we could lock the filters as an owner.
1 vote -
Adding Custom destructive
ANT is unable to change the type on an EmailTemplate from HTML to CUSTOM. To solve that we need to add the EmailTemplate first to the destructive package to have it removed and then add it again with the package.xml
Since this file is not deleted but just changed. It doesn't show up in the deleted items tab.We should add an option to the "Selected Items"/"Changed Items" list to opt-in for adding that to the destructive.
12 votes -
Add default compare filter - Code changed by me today, changed by me last 7
A super common comparison done by a developer is to see only the Apex changes done by that developer today , or in the last x days
Since the last changed dates on Apex (VF, triggers, components) is super reliable whereas it is useless on Custom Field/Workflow), the suggestion applies only to Apex or code-type changes
Gearset would fetch only those code items changed in the last x days, then present in the difference viewer the changes pre-sorted in descending date order
This feature would eliminate multiple clicks just to deploy a handful of recently-made code changes in the comparison…
5 votes -
When running "Compare and Deploy", or via a similar mechanism, allow the target to be a local zip
In rarer situations where I need to make some manual adjustments to the metadata XML for a deployment, I'd like to be able to download the metadata to adjust it. Today you need to go through a compare, and at the end, you can download the package, but this can be problematic, since you have to choose the target org, there need to be differences, etc.
Instead, it would be useful to just choose the source org, select the metadata items, and save the package, without a target org needed.
1 vote -
Allow save into a draft deployment after Refresh Comparison
Use case:
Source is master, target is org
Create draft deployment between master and org; Save
...time passes, new items are added to master
Open draft deployment
Refresh Comparison to see new items in master
Select new items
Click Save Draft Deployment --you have to create a new version (and no obvious way to even see the current draft's name without opening a new tab)Seems like you should be able to save back into the same draft after refresh comparison (or at least have option to do so).
When you create a new version of the draft; you have…
19 votes -
Pending Validation - Copy from Pending Deployment
Similar to "Pending Deployments" It would be nice to see pending validations. We have several users in gearset, so if we are trying to validate something while someone has already initiated a validation, we receive the error that set up has been locked. So prior to validating a package, it would be great to check if anyone is in the process.
1 vote -
Allow changing of public group membership via Gearset
Right now, the only way to edit a group's membership is via the API (users or groups only) or the UI (additionally allows roles, roles and internal subordinates, etc.). Please allow the editing of group membership of public groups.
4 votes -
Allow option to select certain test classes to NOT run. Include an exclusion list of tests not to run
When deploying code, it would be nice to have an option of having an exclusion list of test classes to not run.
5 votes -
Test run details: show failed tests tab first
When user clicks on test run details, Gearset defaults to the successes tab. But no one clicks on test Run details to see successes; they want to see failures. Default tab should be failures, especially if non-zero
Saves user a click and supports DWIM - "do what I mean" when clicking Test Run Details
1 vote
- Don't see your idea?