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
-
2 votes
-
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 -
Filter on selected items
I want to quickly be able to identify components that have not been reviewed by only seeing unselected items in the "Changed items", "New items" and "Deleted items" top level filters.
seeing the ones I have already selected slows down productivity and I have to scroll through them. If I want to see them I can always look at the "All items" section. This information is also available in the difference type column.
6 votes -
add the ability to run static code analysis against an org or source control, simply click refresh button to re-run it and see results
This will give you a "run code analysis -> see results -> fix issues -> push to source control (or an org) -> repeat" workflow.
3 votes -
Possibility to deploy to another sandboxe when a ci job passed
When configuring a CI job, we need an option to set a deployment to another sandboxe when the deployment or test classes run successfully in the current CI Job.
Ex: when a push to a branch on VCS triggers a CI job to deploy to a sandboxe like QA (with test classes run), we also have the possibility to set an auto deployment to staging sanboxe when the the job on QA passed successfully.5 votes -
Show *all* matching items on All Items, even if they haven't been changed.
I couldn't find a field that I was looking for today, despite searching for it specifically, because it was hidden inside it's parent object. I understand that the reason for this was something to do with there being no difference on the field (and I appreciate that the reason is to avoid clogging up the screen!), but if you're searching for a specific field, I think it should really show up...
Took me bothering someone on live chat to figure out what was going on.
1 vote -
Allow to add Custom fields to Source control without Account object in Source control. As we don't want to update existing Account object
Allow to add Custom fields to Source control without objects in Source control. As we don't want to update existing objects in org.
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 -
Better pre-selection of repos & branches
My reasoning for the need:
Every day when comparing, I have to choose one github repo out of 343 (46 of mine + 297 from an org I'm a part of). Yes I know I can type some characters and it will search the list of repos, but it's still unpractical. It sometimes looks like it remembers the choice, but I think it doesn't quite work after logout and I have to select the repo from the long list too often.The bare minimum that would bring me pleasure:
The last used repo I used for any comparison would always…4 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 -
edit other team member's CI job
Have a way to edit other team member's CI jobs, if appropriate permissions are given.
3 votes -
Store formatted JSON in source control
The SFDC metadata API returns some items types as JSON compressed to a single line. For example, this applies to Wave dashboards (.wdash files).
Gearset neatly expands this to a more readable when visualizing and comparing.
However, in source control Gearset stores them in their original one-line compressed format. As a result, when doing merging and conflict resolution at the source control layer, these items are impossible to handle, as any change (whether technically conflicting or not) results in a conflict from git's point of view.
It would therefore be great if Gearset kept the expanded format for JSON data…
2 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 -
Give Permissions to Edit Automated Job Settings
Adding a feature to give users permissions to edit & delete Automated Test Jobs would be great. Today I had to hunt down a colleague to be have him edit his job when all I had to do was change the schedule. This feature would have saved a lot of time.
2 votes -
Offer to push components that passed validation even if some items failed
For large payloads (thousands of artifacts) it can be tedious to try to resolve a few minor issues when 99% of the package will deploy successfully. Having a feature to push stuff that passes validation would be helpful. Included in this in the deployment summary and deployment reports will be a count and list of items that failed validation and were omitted from the package so they can be investigated
9 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 -
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 -
Add the option to purge on delete
The metadata API has a boolean option to "purge on delete", i.e. permanently erase deleted items rather than just moving them to the recycle bin. This option is not exposed in Gearset currently, but rather hardcoded to "false". For CI scenarios in particular, it would be extremely helpful to be able to specify that this option should be set to "true" for deployments.
2 votes -
Allow for custom metadata permissions to be included with a single click when custom fields are being deployed
For example; when adding new custom fields, you generally have to add the permissions as an additional line item to the deployment. Having a checkbox or something that will have gearset automatically add the permissions associated with the metadata currently in the deployment list would speed up the process. Users should also be allowed to deselect lines that were automatically added.
17 votes -
Default to Object View
Option to default to Object View vs XML for metadata types that have it available
9 votes
- Don't see your idea?