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.
369 results found
-
Add a "Clone package" button to the Deployment Results page
My workflow is currently to deploy a change, browse to the deployment history to find my deployment, and immediately clone the deployment for another environment. It would be really nice if the clone button were available upon a successful deployment.
5 votes -
Allow editing all CI Job Fields
One should be able to edit all the fields on a CI Job, especially the source and destination fields.
2 votes -
Upgrade to PMD 6
PMD 6 includes useful stuff like allowing annotations in the code to suppress warnings. It would be great to be on that version.
Stephen told me via the support chat that it wasn't simple to just upgrade, so I thought I would submit it as a feature request.
2 votesHi Aidan,
We’ve now upgraded to PMD 6.3 which includes support for suppressing warnings.
Regards,
Stephen
-
After choosing source/target connection: show friendly name.
When we are selecting source/target we can see the friendly name in the dropdown list.
After the selection is made we can see only the username. It would be easier visually confirm that correct connections are are selected if the friendly name was shown next to the username.
1 voteThis is now completed, and friendly names will appear in the dropdown where you select the org
-
Have a way to exclude objects from comparison
Before using Gearset we used the Force.Com migration tool. We got to learn that several things just can't be deployed to sandboxes so we always excluded them from source control, or learnt to not merge them.
Gearset has filters which mean you can specify things to include, but it would be nice to have things it would automatically exclude for you (i.e. not show in comparison). Some of these it already knows not to try and deploy. Things like
Admin.ProfileUserPermission.EditBillingInfo
Admin.ProfileUserPermission.ManageSandboxes
etc.but there's a few other random pieces that I have to remember to untick each time or deployment…
9 votesYou can now exclude specific items in your custom metadata filters in a similar way to how you include specific items.
This won’t cover some cases, such as excluding subcomponents like specific user permissions within a profile, but for those cases let’s open a new specific feature request.
-
Ability to Clone Button on the Draft Deployment page
Can you create a Clone Button on the Draft Deployment page similar to the Clone Button on the Deployment History page? Some times we collaborate on a deployment and one user will take over. We want to be able to deploy the package as the current user, not the original one that made the draft.
10 votesThe ability to clone draft deployments is now available on the enterprise tier.
-
Active Link to Deployment Destination
When you finish a deployment you get a "Deployment Summary" screen that has handy details. It does not, however, have a link to the commit/branch in Github or other site where the destination ended up. I have to jump to my Github page and refresh instead of having a direct link. Yes, it's a tiny feature but is useful for a Gearset newbie like me.
1 vote -
Validation-only deployment for CI
Add the option to for CI to run validate-only deployments
2 votes -
Clickable Jira Request within Deployment Report
I would like the ability within the deployment report to make the jira tickets clickable. That way a user could simply click the ticket reference to navigate directly to the request.
1 voteThe Gearset has made this feature available for Jira tickets and Azure DevOps work items, thank you for your suggestion.
-
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.
- Don't see your idea?