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.
337 results found
-
Add support for incoming webhooks
There's already a way to set up an outgoing webhook after a successful CI job run.
It'd be nice to have a way for a CI job to have an incoming webhook from another service, such as ElectricFlow (a build platform).
One use case would be for CI deployments to be dependent on external validation services.
4 votesThis is now possible since we have released our API, which is available to everyone with an Enterprise license! Please see https://docs.gearset.com/en/articles/6099550-getting-started-with-the-gearset-api for more details. If anyone has feedback or suggestions, please contact us via the in-app widget.
-
Allow for the masking of data during a Data Deployment
During a data deployment it should be possible to mask the data in specific fields. For example, if I were importing Account and Contact data from production into a sandbox I would want to be able to mask email address so that we can't erroneously send actual customers emails while we're testing
4 votes -
Support "Test Suites" for CI
Hello, Could we make a suggestion for an enhancement? For CI Unit Test jobs, could we have a Test Suite option?
4 votesYou can now specify test suites to run in CI jobs. In each CI run, Gearset will run the tests belonging to those test suites.
Feel free to drop us a message on the in-app chat with any feedback you have on running tests suites in a CI job!
Tom
-
Provide reporting capabilities for Deployment History
Our executive sponsor for Gearset has asked me to provide him with some metrics around our Gearset usage. Specifically, we would like to be able to have access to some of the data that already exists in the Deployment History section, but in a format where we could report on it. Ideally, we'd be able to show how many deployments to production, how many components deployed in those packages, frequency of production deployments in a given timeframe, etc.
This would be a very valuable feature for us so that we can ensure our executive leadership team is briefed on the…4 votesThe deployment history can now be exported as a CSV file that will enable you to create the metrics you’re looking for.
Regards,
The Gearset Team
-
CI job option "hardcore" - The deployment should fail if the static code analysis identifies errors
For CI jobs we would like to have an option that validation or deployment fails when code analysis identifies any "Error" in the Static code analysis.
4 votes -
Live chat button overlays action button
Not sure how you resolve this one without moving either button. Maybe do something similar to what is done in the Diff view (where the action buttons are displayed in a row below the content).
Another option would be to have the live chat in the header navigation to toggle the feature on / off?
Not sure...Just noticed that it gets in the way sometimes.
4 votesWe’ve now made sure that the Live Chat button doesn’t appear on top of any of our action buttons.
Let us know if you see this one creep back in!
-
Specify friendly name before deployment
We would like to be able to specify the desired friendly name before a deployment completes, maybe above notes on the summary screen. The friendly name is copied from an existing draft, but when we clone from sandbox to sandbox and finally prod, there's no need to save a draft every time. Ideally, the friendly name would default to that of a cloned deployment as well.
4 votesThe ability to name the deployment from the pre-Deployment screen is now available, and will be used as the friendly name.
-
Add support for Visual Studio Team Services git repositories (Hosted TFS Git)
We use VTFS for version control hosted or OnPrem SVN for version control. Our enterprise architecture team has determine those are our 2 options for source control and Gearset doesn't support those options.
4 votesThis is in Gearset now. Try it out and let us know how you find it!
-
Remember a default Github repo
I have access to a huge number of Github repos but use only one for gearset deployments. It would be nice if that repo were automatically selected.
4 votes -
Persist a customized comparison config when starting a new comparison
If I choose to compare specific types using the Customize Comparison feature - Gearset Deploy should remember those choice(s) when I start the subsequent comparison(s).
4 votesYou can create and save custom comparison filters from the dropdown underneath the “Compare now” button on in the app.
-
Refresh Comparison enhancements
When doing a "Refresh Comparison", allow only refreshing the source. Or to only refresh the selected items from the source and/or target.
Example, deploying from a git branch to a sandbox, refreshing the metadata takes a few seconds from git, several minutes from the sandbox (target).3 votesWhile not exactly one-to-one match, we think this UserVoice already delivers the desired outcome:
Thank you for upvoting this UserVoice request!
-
I would like the option to view the delta CI only changes within the comparison, like the agents who are helping me untangle issues
I would like the option to view the delta CI only changes within the comparison, like the agents who are helping me untangle issues. ask kevin slattery to show you.
3 votes -
Show deployment friendly name on Deployment successful page
On the "Deployment successful" page, I'd like to see the Deployment friendly name displayed. This would be much more useful than the Salesforce Id that is currently displayed.
3 votesReleased this week
-
New Analyzer to prevent endpointURL changes for Outbound Messages in Sandboxes
A major pain point and blocker to use automated CI jobs is that we cannot include workflow rules because we have outbound messages set up to specific test endpoints per sandbox/environment. As the workflow metadata type allows us no ability to filter by workflow rule name (it's by object), this means we have no option but to manually run the comparison and deployments for each of our sandboxes.
It'd be great to add a problem analyzer to suggest not changing the endpointURL field on outbound messages when the target is a Sandbox. This way, you can deselect it manually when…
3 votes -
Ability to create Pull Requests for AWS CodeCommit
Gearset can create Pull Requests for many of the source control systems that it integrates with, but not AWS CodeCommit.
As AWS users, it would be very useful to use to have this ability so that we didn't need to switch systems to create Pull Requests.
3 votesThis functionality was implemented in February 2022.
-
Export subset of data in data backup
I would like to be able to filter what I want to export from a data backup, since I probably won't need everything from the database. This would make the downloading more manageable.
Ex: Export only ContactID and Email fields from Contact object from a specific backup.
(Restore data seems to allow this, but in this specific case I needed to run some checks in Excel since I couldn't just update everything with the old data)
3 votesYou can now select the object(s) to export for a particular backup run.
Simply go to the backup history for a job, and for a backup run, choose the ‘Download data’ option in the context menu to choose the subset of data that you’d like to export.
-
Treat "New" FLS entries that don't grant any access as "Not Different" in Profiles and Permission Sets
Due to a recent change in the SF API, Permission sets now display every field in the org as a "New" FLS item, with Readable and Editable both set to False. This is leading to two distinctly negative results.
1) For every "Permissions for FieldNameXXX" item, every permission set in the org is modified. If two projects on two different sandboxes each add a field, they will both modify modify all the same files, and require manual XML merge. for our org thats almost 70 files that need manual merge with every new field.
2) When you dig into a…
3 votes -
Allow multiple Team owners to Connect to the bitbucket server through OAuth instead of creating a new link every time with in same Org
With in an org if we have multiple owners working as multiple teams, Gearset should be able to allow other owners to connect to the same Biibucket server through OAuth, instead of creating a new link every time.
3 votesThis was completed and released on 22nd of January 2020
-
CI dashboard: Show commitId when job is in flight; Show queued commitIds
On CI Dashboard page, a CI job in flight (deploying/validating) should show the commitId that triggered it (if any) PLUS show all pending CI jobs.
Reason: If two developers are sequentially merging to a shared branch tied to the CI org (and webhook is setup to run immediately), then the first developer's merge starts CI job 1 while the second developer's job is queued.
Yet, from the CI job page there is no way to even tell which commit to the branch is running (so as to clue the developer that his/her job is running vs queued. Commit message would…
3 votesThanks for the suggestion! When a CI job is running from git, the commit hash and the commit message is now visible for all git providers. In addition, for GitHub, Gitlab and BitBucket sources, a link to go to the relevant commit will be displayed.
-
Stamp Deployment Results with Salesforce Id of the Deployment package for auditabilityq
When a deployment is successful, the deployment results/report should include the Id of the deployment package from Salesforce. This would create a foolproof audit trail between Gearset deployments and when they went into effect in Salesforce.
3 votes
- Don't see your idea?