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.
1150 results found
-
would be cool to be able to "ignore" certain differences
would be cool to be able to "ignore" certain differences... e.g. encryption. So if encryption is enabled in a Production Org but not in a Sandbox (not sure if Encryption is possible for SBs), you have a difference for every custom field <encrypted>true/false</encrypted> which is really irritating.
16 votes -
Deployment of pre-valided package doesn't include accurate test counts
We did a deployment last week and noticed that as part of the deployment report that went out that it stated the Tests Run was zero. We did a pre-validation the day before where we ran all tests with all passing.
Could this test section on the deployment report again include/include the pre-validation tests that were run for the deployment?
3 votes -
Allow teams to share custom git repositories
It would be nice to be able to share custom git repositories with the entire team. At this time, each team member that does deployments needs to configure each custom git repo in Gearset. Besides requiring them to set it up, it also means I need to give each person the credentials.
4 votes -
Allow for selecting which repositories to display for github in org settings.
It would be helpful to be able to select repositories to display in the selection under Manage Orgs. Some of our repos in Github aren't related to Salesforce deployments, and filtering those out so they don't even show in the list would be really helpful in getting to selections faster.
10 votes -
Support aliases for metadata types in the search box
So often, I type something in the search box for a metadata type based on the point-and-click force.com labels and the search comes up with nothing.
I'd suggest an auto-substitute option so if one types in 'Email alert', it auto-prompts for the metadata API substitute: 'Workflow alert' Or, if one types in 'Support process', it auto-prompts to substitute 'Business Process'
1 vote -
Include a field's permission if the field is flagged as a missing dependent component
If a field is identified as missing from the deployment and the user agrees to include it, the corresponding field's permission should also be added.
4 votes -
Automated User Test Suite Integration
Such as Selenium and/or Cypress.io
7 votes -
Provide the option to skip problem analysis
Sometimes during a complicated deployment I need to try a few different strategies to get things to work. For example, I may need to just send up one piece or set of metadata up first.
The problem is, each time I do this, I have to wait for problem analysis to complete, which takes a couple minutes. Normally during a deployment I do want problem analysis to run, but if I want to quickly send up a single object, I have to wait a few minutes while Problem Analysis runs, and the time waiting adds up.
Maybe a quick deployment…
6 votes -
Filter out Custom Field differences based on Field Tracking History
If the only difference in the field is that History Tracking is turned on, it would be nice to filter these results out.
Running checks on our app with multiple customers, who all set history tracking differently, can create a lot of noise to filter through to find actual differences.
3 votes -
Custom text within automated emails
I simply want to be able to add some lines of text to the emails that are triggered.
In our case this would simply be to let the team know the deployment was complete please proceed with any manual steps for example. In our org this would simply save a step for the release manager to have to trigger an email stating this and be included in the email triggered by gearset.
This functionality might also play out nicely that we could have some more specific text around the test jobs that we trigger. For example, we have thought to…
1 vote -
AWS CodeCommit ability to view Repos
Today the ability is not there to allow for viewing multiple repositories within AWS Code Commit. One can view a singular repo and the branches that it contains.
In our instance we have different repos for our various instances. We would like to be able to have the ability to go on level deeper and be able to first choose the repo, then choose the branch.
Hit me up with any questions please.
2 votes -
Add search specific item history
For monitored environement, it would be great to have the ability to search for specific item history.
1 vote -
Error while deploying dashboard component using Changeset / Gearset / ANT
This is a common error received during deployments:
Error: Metric, gauge, or table dashboard component missing indicatorLowColor attribute (line 70, column 33)
This is a suggestion to Gearset team for there feature Deployment analysis if they would pick this error in advance before deployment.
Observation: This issue occurs when the Dashboard is created in Lightning. (I cannot confirm though)
Resolution:
Downloaded package.xml and component
Basically, after I pulled the dashboard metadata from source org, I opened it and found the
<componentType>Table</componentType> tag, and right under it I added this:<indicatorHighColor>#00716B</indicatorHighColor>
<indicatorMiddleColor>#ffb75d</indicatorMiddleColor>
<indicatorLowColor>#C23934</indicatorLowColor>After this change I managed to deploy everything…
1 vote -
Add a validation/warning for when users try to filter only permission set for comparing and deploying
we believe that if we are given the option to filter only permission sets for the comparison, there should be some type of validation ensuring that you are also including dependencies such as custom objects, apex classes etc so that we don't make the assumption that filtering permission sets only in the comparison will include all dependencies
1 vote -
Allow comparisons of a single commit from a VCS
Currently, you can select a VCS repo and branch to use for comparison. It'd be great if you could select a specific commit from that branch, so that you're only looking at an atomic set of changes. This would allow for fine-grained comparison and deployment of changes.
9 votes -
Create a VSTS Build Task for Gearset
VSTS offers the ability to create build definitions to validate/deploy your code, but Gearset customers don't have much options natively in VSTS to trigger a Gearset deployment. We can scan a code repository for changes every 4 hours in order to do a CI deployment-- but that's about it.
VSTS offers the ability for vendors to create "Build Tasks" for their applications, where you can initiate a VSTS build and get results. This is basically a controlled version of API access to the tool.
More information:
VSTS Marketplace - https://marketplace.visualstudio.com/vsts
VSTS "Add a Build Task" - https://www.visualstudio.com/en-us/docs/integrate/extensions/develop/add-build-taskIt would be…
2 votes -
Test job triggered by CI job
Test jobs are only configured on time basis. When developer commit some changes and it will be deployed, but tests will be done on a time basis in 2 hours for example, so he should wait to know weather tests are passed or not. Or ask the release manager to run tests manually. So, this feature is must have improvement.
1 vote -
Support grouping of Manage Orgs page
Support the ability to group org credentials on the Manage Orgs page by a new Group Name attribute. In managing multiple clients with dozens of PRD and Sandbox orgs it would be extremely helpful to be able to group and filter related credentials by client. However, to expand this feature to support multiple use cases, providing a new Group Name attribute (text) which could contain any value would be fantastic!
Thanks for your consideration,
Mike1 vote -
Integrate with Jenkins
Build a Jenkins Plugin to integrate with Gearset that would allow triggering CI jobs and/or deployments.
6 votes -
Allow a deployment team to update the same draft deployment at the same time or warn the end user of a draft in use by another user
When a dev team work on a shared deployment, it would be nice to work on the same deployment draft, at the same time. At a bare minimum, it would be good to be warned that someone is updating the draft at the same time as you.
1 vote
- Don't see your idea?