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.
334 results found
-
Remember my default source control system and default to it
We use Bitbucket not git hub. So on compare metadata screen when I go to Source Control radio would be nice for the version system to default to bitbucket.
Small tweak I know but annoying to change every time. Easiest might be that the drop down list stays set to whatever system you used last?
3 votesHi Douglas,
I’m marking this as completed because this feature is already implemented and should remember the last VCS system you used – if it isn’t working then that’s a bug!
Note that it’s currently only implemented on the Compare and Deploy page, and is specific to the source/target (so using Bitbucket on the source side won’t carry over to the target side until you’ve used Bitbucket once on that side, and vice versa).
The preference is only saved when you actually kick off a comparison. Clearing your local storage for `app.gearset.com` may clear up any issues if you’re having problems.
We’d love your feedback if this isn’t working or isn’t implemented as you’d expect it to be.
Thanks,
Oli -
View deployed components from a CI Job
Display components deployed via a CI Job. In my case, there are a greater number of total objects deployed than I would have expected; but, I have no way of viewing the comparison for what is automatically being deployed.
6 votesGearset now supports viewing the underlying comparison that ran as part of your CI job.
Press the `View comparison` button beside a particular entry in the CI history to see the components
-
A way to view failed deployments from Gearset
Right now if a deployment fails in Gearset, it doesn't show up anywhere within Gearset; it just sends you an email. It would be nice to have a place to view failed deployments and retry them (maybe it only failed because the environment was locked), just like you can with successful deployments in Deployment History.
3 votesGearset now shows failed deployments on the deployment history page: https://app.gearset.com/deployments/deployed
-
Ability to pause CI jobs
Ability to pause a CI job. This would allow the CI system to keep our sub environments (stage, dev, beta) updated all the time, but when we want to develop on one of them we could then pause the CI job so our changes don't get deleted. Then once we have deployed the changes to prod we can reactivate the CI job to keep things in sync.
5 votes -
Prev/Next buttons did not function for setting the focus when in APEX view mode
When viewing an Apex class with differences, the Prev/Next buttons did not function for setting the focus in APEX view mode however they did function when in XML view mode.
2 votesWe’ve identified and fixed the issue. Thanks for reporting it.
-
Under deployments in the validated tab there is no column for the name of the deployment. Please carry over the friendly name.
When a draft is validate, as the gatekeeper for production I cannot see what a coworkers validated deployment is about. It seems like the friendly name should carry over as a column to display on the validated tab, also into the deployment history.
10 votesThis is now implemented and released. As on the deployment history page, you can now name your validated packages.
This name will follow over from a draft deployment and to the deployment history.
Thanks for the feature suggestion!
Oli
-
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!
-
Run external tools like PMD as part of Schedule Tests/Monitor Org
PMD tool that does apex code 'quality' measurements would be kind of cool to run (optionally) as part of a regular monitoring/test job. This could be generalized to any external tool
1 voteGearset will now run PMD to track code analysis as part of the Monitoring and Backup flow. The plan is to roll this out to other parts of the app so we can more easily track the change in code quality.
-
Online help for Manage custom filters
For large Orgs, doing a comparison with the default set of metadata types can take a long time, and so it is necessary to select a smaller subset of metadata types to compare.
However sometimes it is not obvious how a particular configuration change in Salesforce relates to the metadata types in the custom filters dialog, and what dependencies exist between them. For example, after changing "Override" settings in the "Transalation Workbench" in Salesforce, it is not immediately obvious that you need to select both "Custom object" and "Custom object translation" metadata types in Gearset, rather than the "Translations" metadata…
1 voteGearset now links to the metadata documentation for each Salesforce type.
If you think there is more information we should be displaying, or if you’d like some custom documentation, then just let us know!
Thanks,
Kevin -
What does the "Unknown" value mean in the Changed By column
How should I interpret the "Unknown" value under the Changed By column when viewing comparisons? In what scenarios would the value Unknown appear? Please advise
1 voteSalesforce does not return the full information for the changed on / by for some metadata items via the API. In these cases you’ll see “Unknown” as the changed by. This is typically components of larger objects, such as fields on a custom object. Gearset shows these as discrete components which can be deployed, but Salesforce generally only returns the changed information for the parent object. We are hoping that over time, Salesforce will improve the reporting of the API to include more information for these sub-components. As soon as it does, we will display that extra information. Hope that helps.
-
Allow for test options from Validated Packages tab
After validating a package, the Deploy button under the Validated Packages tab should offer the same test options (No tests, Specify tests, etc.) as it does during the normal deployment workflow.
1 voteThis can now be done by clicking the new Details button on a validation, which will take you to a page which includes the normal deployment workflow button with testing options.
Thanks for the suggestion!
- Oli
-
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 -
Disable scheduled tests (temporary)
We're currently using this tool primarily for nightly unit test monitoring. However, some nights we don't want the tests to run because we'll be doing after-hours upgrades and other maintenance.
As far as we know, currently the only way to 'disable' the automatic test run is to delete/disconnect the app entirely. However this is not ideal, as we have to re-add/re-auth to turn it back on.
If Gearset had a checkbox next to each org/environment that we could enable/disable the job at will, that would be ideal.
7 votesWe’ve now released support for this. From the https://app.gearset.com/test-monitoring page you can temporarily disable test jobs and then reenable them later.
Thanks for the suggestion!
-
Add the ability to define which Apex Test's are run during the validation phase of a deployment
I would like to suggest a new feature request. We have a great need to define which apex tests are run against the Target ORG due to special configurations. We have apex classes / test classes that are created in Target ORG's that are client specific. For example, if we go to deploy our managed package from Sandbox A -> Sandbox B, the tests may fail since the content in Sandbox A needs to get to Sandbox B before the client specific changes can be updated / tested. There are multiple parts to our product and adding in the ability…
2 votes -
Filter on Columns in comparison screen
On comparison screen, would be nice if we can filter on each column on top of standard string filter
Example use case: Show me Custom object with last modified by me with modified date within this week.
Can be achieved if we can filter on "metadata type", "Changed on", "Changed by" Columns
5 votesWe’re closing this feature request as the main bulk of functionality (more advanced filtering on a per column basis) was implemented at the end of 2016.
If you have a specific interest in 1st class filtering specifically by date, could you open a new feature request for that?
Thanks,
Gearset team -
Allow search-based excluding of metadata for templates
Sometimes we have individual metadata that must be excluded-- every time-- from releases, without excluding the entire metadata category.
For our organizatin, for example, we want to exclude "Search" every time due to an error-- but we don't want to exclude the "Settings" metadata item.
It would be great if we could add specific exclusions to the template so that a specific metadata item would not even pop under the Compare screen. Doesn't really matter how it's done (fuzzy searching or specifically excluding standard items) to me.
2 votesThis work has now been completed, and you can specifiy individual items on the metadata filter.
The doc is available from https://docs.gearset.com/feature-guides/comparisons-and-deployments/custom-metadata-filters
Thanks,
Kevin -
CI Jobs - Partial Deployments
Allow partial deployments when changes are committed into a branch, so instead of trying to re-deploy the full repo, we should have an option to allow deployment for only the changed items.
6 votesCI jobs can now be set to deploy only certain types of metadata change: new, changed, deleted. If only “changed” is selected, no new metadata or deletions will be pushed by the job, only modifications to metadata that exists in both source and target. This selection is found in the job creation/edit screen. You can also specify whether you want the CI job to respect a package.xml file when deploying from a repository for even finer control over what metadata it deploys.
-
Changed By / Change On reporting incorrect user
Changed By / Change On reporting incorrect user when comparing to Salesforce orgs (sandbox to prod)
2 votesI’m going to close this post. Unfortunately Salesforce provides the information and we’re simply reporting it so it’s beyond our control. I’ve provided 3 scenarios in the post about what can happen. I’m sure we’ll uncover more over time!
-
Create CI deployments which only run on demand
Have jobs that run only manually, rather than on time or commit basis.
Specify the source and target and the metadata filter, and save as a preset job. The job can then be triggered to run on demand with a "Run now" button. This means we can safely update our branch until ready to deploy, then don't have to manually compare orgs to push the changes out1 vote -
add linked services to "Reuse deployment package"
When cloning a package that was originally deployed to a github repo, the dialog for "Reuse deployment package" only has source/destination Salesforce organizations and not linked services like github.
2 votesThanks for the feedback, this was a great suggestion. We released this feature last night – if you clone a package you should now have the option to choose from Salesforce orgs or linked services such as GitHub.
- Don't see your idea?