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.
1140 results found
-
Show the commit message with the Commit ID on the CI History Screen
The CI Job History Screen would be much more useful for me if it was able to show the commit message on the commit that triggered the CSI alongside the source commit ID.
2 votes -
Allow Downloading of git diff for Comparison
It can be difficult to evaluate the scope of changes by clicking in the Comparison view on one metadata element at a time to see the differences. We would much prefer to be able to download a git diff and examine the delta as a cohesive changeset.
The user should be able to download the contents of the currently selected tab (All Changes, New Changes, or Selected Changes) in the format of a git unified diff. The user can then use the software of their choice to view the diff.
This will also enable more advanced workflows, as git diffs…
2 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 -
2 votes
-
Deployment Notes Persist on Failure
When a deployment fails, deployment notes are sometimes wiped, and it is laborious to retype them - sometimes, I'll copy and paste to Notepad before deploying because I know I'm going to have to type them again. Notes should persist, or at least be configurable, from one comparison run through successful deployment.
2 votes -
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 -
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 -
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 -
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 -
Be able to start immediately a JOB (CI/Unit Tests/Monitoring)
Add a button to start it immediately. Currently only solution is to change the executing time!
2 votes -
Allow bulk org access for new users, new org permissions upon adding
When adding a new user having the ability to give the same level of access to all orgs at once would be greatly beneficial.
Likewise, when adding a new org and having the ability to set user access to the new org would save time as well.
We are adding new orgs frequently and will be adding users as well. Saving time on permissions would be great!
2 votes -
test Monitoring overview - show "is running" + stats
On the Test Monitoring Overview page; you should be able to see at a glance whether the test is running and how many methods have run vs total
Reason this comes up is if you establish a Unit Test run for your developer sandbox org, then you can't run (some) tests from your IDE against the same org "ALREADYINPROCESS Test already enqueued"
A quick glance at the Test Monitoring Overview would tell you if you need to wait 1 minute vs 20 - and guide your activities accordingly
2 votes -
Support parallel testing during CI job
CI jobs use metadata API to deploy and run tests. The tests run serially. As such, CI jobs can take many minutes to execute
As an optional configuration for a CI job, and only if the CI is run against a non-PROD org...
- Deploy metadata using Metadata API
- Run tests using Tooling API (parallel testing)
- If tests fail, use MetaData API to rollback the deployment
Ideally, this can shave off 50% of the CI job time
2 votes -
2 votes
-
Suppress "changed on" datetimes in difference viewer where datetime is the same as the metadata retrieval datetime
The difference viewer will show Changed on values for the current datetime for certain metadata types - probably because SFDC is returning such a value when, in fact, the source didn't change at all
- Custom object
- Settings
- Standard valueset
- Workflow rules
displaying the current datetime of the compare run (i.e. the metadata retrieve datetime) is not helpful when trying to filter on changed date in the difference viewer (i.e. sort descending)
2 votes -
Enhance capabilities around 'co-administration'
In our organization we have a couple different salesforce admins that are administrating the salesforce development pipeline in which several developers are making changes and deploying them via gearset. Right now it seems cumbersome/duplicative to do this particularly around the area of adding a sandbox org and then managing permissions of the developers to that sandbox. It would be nice if there was a way for one admin to connect the sandbox, grant the other admin "Owner-level" access to it, and for the two admins to have a shared view of the user access to that org, so I can…
2 votes -
Create a Master-Switch Only deployment process
Can you create a master-switch deployment option? It would be similar to how this operates: https://sfswitch.herokuapp.com/
The issue is that this master switch does not always work with managed packages in production orgs.
So a way to automate the turning off/on of Validation Rules, Process Builders, Flows, and Triggers.
Use Case: We are building a new app and have significant data migration to do. It would help to have a master switch to turn off processes in PROD, deploy date, then, flip the master switch back to turning processes back on.
2 votes -
I have so many connections and jobs, is it possible to have group them (in future release?)
I have so many connections and jobs, is it possible to have group them (in future release?)
2 votes -
Optimize comparison list view
The comparison view contains a list view in a scrollable area with an line item for every metadata item in the comparison. Depending on the comparison, this list can be exorbitantly long (10k+ lines). Displaying this many elements on screen is extremely inefficient, and causes browsers to lock up when selecting the "check all" check box (because it results in thousands of incremental manipulations in the DOM). This issue also causes mobile browsers to crash when more than a thousand or so items show in the comparison results.
There is a common pattern for handling long lists like this, in…
2 votes -
Allow (restricted) editing of source XML to add deployable properties that can't be fetched via Metadata API
Example:
It is impossible with OOTB Gearset to deploy an autonumber field with a starting number and optional populate existing rows. Why? Because the SFDC Metadata API as of V42 doesn't allow fetching of these two properties of the CustomField object:<populateExistingRows>true</populateExistingRows>
<startingNumber>1</startingNumber>Once in source, they'll deploy just fine to the target org. Note that changesets support this feature.
The workaround, which is to deploy to target branch and then edit target branch is sort-of-OK but it would be nice to modify this in the source. Of course, if you Refreshed Comparison, your edits would be…
2 votes
- Don't see your idea?