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.
360 results found
-
Notify Slack when deployment is successful
I would like to inform Slack on when a manual deployment is successful or failed. It will tell me what the source environment and what was the destination environment. It will also tell me if what the success/fail ratio of the tests that were run.
30 votesYou can ask Gearset to post to Slack or MS Teams when a manual deployment succeeds or fails to all or specific connections (including orgs and Git). See more:
-
Preview Deployment Details in Deployment History
On the Deployment History page, it would be nice to have a little popup window to view some of the files from the Deployment Details instead of having to download the Deployment Report
7 votes -
Show a browser alert after a long running operation
Some operations, such as a comparison or deployment, can take some time. I normally navigate to another tab. It would be good to get a browser alert when the operation is finished and I'm needed again
1 voteThis has now been completed
-
Create the ability to migrate components to new source and target orgs after having in a Saved Drafts.
When saving components into drafts, when validated, we would like the ability to be able to migrate the same components into new source and target orgs.
8 votesHi,
You can now use the new clone feature for any saved draft deployments if you’re an enterprise tier user.
Regards,
Stephen
-
Be able to edit the CI sync frequency
When creating new CI job from one Salesforce org to another, there is no way to edit the frequency of synchronization. It would be useful to make a change so that integration is done less often than every 4 hours
9 votes -
Remind me what I just validated
I am working on 10 things at the same time like usual. I started a validation about an hour ago. I open the tab where the validation was occurring and it says it succeeded. Yippie! Problem is I don't remember what I was validating and nothing on the success screen tells me which system I was validating against. I want to be sure I am going to deploy the right thing to the right server at the right time.
Can you add the name of the destination system (at least) on the success screen so I can remember what I…
1 voteThis information is now displayed on successful validation.
-
Gearset API to externally trigger Gearset actions
It would be incredibly helpful to trigger Gearset comparisons, validations, deployments, etc. from an external source using an API. Our team uses GitHub for our VCS, which provides the perfect opportunity to:
1. design webhooks to validate changes in order to approve a Pull Request
2. design webhooks to automatically deploy changes to an org once the PR is approved.Additionally, CI tools such as Jenkins, TravisCI, TeamCity, etc could use such an API to design complex builds that still employ Gearset, but use the external tool for additional actions outside of what Gearset provides for their CI features.
108 votesThis is now 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.
-
Include select all option for Manage Custom Filters
Selecting individual items to include for custom filters is a laborious process. We have to exclude 6000 items and we are unable to do this manually. Please add the select all option when using a filter in the manage custom filters dialog so multiple items can be selected at once.
1 voteGearset now has a `Select all` option for named items on custom filters.
Thanks for your feeback!
Thanks,
Kevin
CEO, Gearset -
Include ability to add inclusion/exclusion option for custom filters
For custom filters we need to exclude objects that are non-relevant. Most often these are managed packages (eg. fflib*, al, rstk__, etc). The only way to do this currently is to deselect all items and manually select each item individually. Not only is this a laborious process, this means that anytime any other new objects are created, these custom filters will ALWAYS need to be updated in order to include them. An inclusion/exclusion filter offers greater flexibility and is maintainable. The current approach is neither a manageable nor scalable process for a large development team. Alternatively, add…
2 votesGearset now supports regular expression in custom filters, so you can write these kinds of rules
-
Display API version underneath source and target on Comparison In Progress and other pages
When deploying from org to GIT or vice-versa, the API version being used should be echoed (small font) everywhere the source and target names are shown (such as at top of Comparison in Progress)
This is especially important for GIT where Gearset in the absence of other info will default to V37 that in turn causes issues with picklist comparisons. It can also be important during Sandbox Preview of new releases
1 voteWe’ve now shown this on the `In Progress` page.
If there are other places you’d like to see it, then feedback always welcome to submit an idea for that specific page!
Kevin
-
9 votes
You can now export the results of the static code analysis as a csv file from the main deployment workflow, change monitoring results for an org and CI job runs.
-
Gearset integration with Jira hosted on local Server
It will be great to have Gearset integration with Jira hosted on local Server. Currently, we have only with JIRA cloud.
Thanks5 votesSupport for on premise Jira was added in January 2018.
-
Support more than one Dev Hub (sfdx) per Gearset Account | Manage Orgs
The Manage Orgs tabs only allows one to have at most one Dev Hub. This can be limiting in the following use cases:
Your Gearset user account is associated to a PROD org that has Dev Hub enabled yet the Gearset user wants to experiment with sfdx and Gearset using the SFDC Trailhead-recommended 30 day Dev Hub Trial Org
You are a consultant working with multiple clients, each using SFDX and hence each with their own Dev Hub. Yet as consultant, you have only a single Gearset account.
3 votes -
Add column filtering with org type(s) in deployment history
Ability to filter on org and/or org type in deployment history so we can easily view which deployments were made to which orgs. For example, filter to only return deployments to production orgs.
2 votesWe’ve now added more advanced filtering to the deployment history page to enable multi-selection. You can find the filter menu via the dropdown next to the text search box.
-
Static code analysis - allow for exclude patterns on classes
The new static code analysis feature using PMD is a good first start but there are too many false positives to make this useful
Here is one place to start:
Allow for specification of regex patterns to exclude classes. Specifically, classes that start with xxxx_ would be most helpful as it would allow us to remove from analysis unmanaged packed code like fflib (Enterprise Patterns) or sfab (SobjectFabricator). There are hundreds of lines of PMD rule alerts from these classes
1 voteTeam owners can specify exclude patterns on the rule set configuration page.
-
Allow selecting a metadata comparison filter when editing a existing job
For monitoring / backup and CI jobs, when looking at the Metadata Filter tab, it would be great to be able to select from the Metadata Comparison Filter. Sometimes I want to be able to reapply a custom filter.
Specific example - I have a monitoring / backup job. Originally it was comparing 65 metadata items. Later, I changed the filter to compare all 96 types of metadata. Now, I want to undo my change. How do I get back to the original 65 without manually unchecking each type?
Thanks!
2 votes -
Run Tests During CI Jobs
There are some similar but not exact posts below so I'm writing about a new one. We would like to be able to specify an option to run tests when deploying via a CI job from git (Bitbucket) in our release sandbox. If any of the specified tests fail, the CI job would fail and the deployment rolled back. It would be great is we could specify whether to roll it back or not when configuring the job but if that is too much too bite off, just failing the job would be helpful. Thanks!
3 votesIf you edit your CI job then you’ll have four options:
1. Default test behaviour
2. Don’t run any tests
3. Run only your tests
4. Run specific testsYou can select the test level that you’d like for your CI job and it will be respected and pass/fail your CI job accordingly.
Thanks for reporting and I hope this helps!
Kevin
-
Export Comparison details all items
In the comparison details the tab "all items" it should have the ability to export the table
1 vote -
bug -- Refresh comparison with a selected item that on the refresh is no longer changed
If you have a piece of metadata that was changed on a comparison then a subsequent comparison using the 'Refresh Comparison' button. The selected item is still selected and unable to be deselected.
1 vote -
Trialforce ORG Type Support
Hey Gearset!
I want to do some testing with the Data Deployment beta feature, and i realized something. Most of my testing is done on Trialforce ORG's (Trial ORG's that are generally identified as a production type ORG). Is there a way that we can delineate between true production ORG's and a Trial ORG and have the Trial ORG as an option to deploy data to? Current options are Sandbox, Developer, and Production.
Thanks!
Richard Scott - AHM
1 vote
- Don't see your idea?