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.
1394 results found
-
Add Additional Deployment Preferences for JIRA integration
Currently the Jira Ticket Deployment Preferences don't give you enough options to manage the expected behavior with our process. Right now there is too much noise on our tickets and we want the option to reduce that. For example, we do not need to comment on the ticket when attempting to validate deployment, just as we don't need it for failed deployments (which you already have as a feature). We simply want a comment with the deployment notes when a deployment is made since this would reflect the actual system changes that took place with this feature/issue.
3 votes -
Show test apex run in the deployment report
When we validate a deployment then schedule it for deployment. Once deployed we receive a report however the tests run do not show here and you have to back to the validated section to find them - please include the tests run on the final deployment report
3 votes -
Be able to log into scratch org from Deployment Success page
It would be super convenient to log into the scratch org directly from the Deployment success page
- From Compare & Deploy sequence
- From CI success
3 votes -
Allow outgoing webhook option to be configured for Compare and Deploy
I need the option to configure an outgoing webhook when deploying via 'Compare and Deploy' feature. Currently webhooks are only available with the CI jobs.
3 votes -
3 votes
-
Add ability to customize CI Dashboard
We have a number of different teams using Gearset with a number of different CI jobs. I don't care to see their jobs in my dashboard and they don't care to see my jobs on their dashboard. It would be great to be able to customize my dashboard so that I only see the jobs I'm interested in. Maybe it's some sort of flag on job to be able to add/remove from dashboard or maybe its a separate tab called 'My CI Jobs Dashboard' that we could default to when opening CI Jobs. Thanks for your consideration.
3 votes -
Add an option to not run the comparision part in CI job (sfdx like)
When you are pushing a project with sfdx, there is no compare, sfdx just push the whole package.
It will save a lot of times.
3 votes -
Add Provar integration for testing to support companies that already have investment in Provar.
Integrate Provar for testing.
3 votes -
Metadata filter - ability to select Report/Dashboard folders by parent folder name
When setting up a metadata filter for a new comparison, when it comes to Reports and Dashboards, it would save sooooo much time if they could be selected according to the top-level/parent folder that they reside in. That would enable the ability select all reports within a single parent folder at once, rather than having to select reports separately which reside in a nested/child folder.
3 votes -
Monthly sandbox refresh from production
I would like the ability to refresh a sandbox from production on a scheduled recurring basis on a monthly cycle (ex: from prod to a full sandbox) so as not to overwrite current development items that are in process or testing.
3 votes -
Ability to change Formula Fields to other Field Types
Gearset doesn't help with one of the most common deployment headaches: changing a formula field to a non-formula field type. It's still a nightmare even with Gearset.
What would be awesome would be if you had a "Change Field Type Wizard" where we could say FormulaField1 needs to become TextField1 and it would do multiple deployments to accomplish the changeover:
- get components
- deploy temp field of new type AND update all existing components to reference the temp field instead of the formula field
- deploy delete of formula field
- deploy text field in place of the old…3 votes -
call webhook with scheduled deployment
We would like Gearset to call a webhook when a scheduled deployment completes. The message to the webhook should pass a message with the org name, UTC datetime, the deployment friendly name, URL of Gearset deployment results and a status field with 'succeeded' or 'failed'
3 votes -
Provide integration with WebexTeams
We moved from Slack to WebexTeams and have lost the ability to post deployment notifications from Gearset. Here's an article about Webex Bots: https://developer.webex.com/docs/bots.
3 votes -
Find/Replace before deployment
Allow a basic find/replace to run against files before final deployment.
Examples: a username that would work in the sandbox that does not exist in production and we need to change it. Or deploying to a packaging org required a modification due to various namespace issues. Other tools have a means to do this in one way or another.3 votes -
Clone Package - keep Tests list
It would be great if when cloning a deployment, it can keep the tests which got performed in the original deployment. Right now, we need to keep a list of the tests which ran on a doc on the side.
3 votes -
Deploy data from local repository.
It would be very helpful if we could deploy data from a local repository. We have different namespaces for internal packages and it would make data migration significantly easier if we could do it from a local machine where we'd switch the namespaces.
3 votes -
Ability to tell what metadata filter someone used in a compare/deployment
For compliance, troubleshooting, and collaboration purposes it would be great to see what metadata filter a user used on their comparison
3 votes -
Remove the "run as specific user" completely from the dashboard prior to deployment (set the options to "Run as
Add during problem analysis:
Remove the "run as specific user" completely from the dashboard prior to deployment (set the options to "Run as logged-in user"). Deploy, then change it back to whatever you need. Based on https://developer.salesforce.com/forums/?id=906F0000000DCJPIA4
3 votes -
Deploy SOAP APIs like Permissionset assignment
I am able to deploy profile components and permission sets separately. But the permission set assignment is part of salesforce SOAP API and I couldn't deploy the same using GearSet.
Kindly provide deployment options not only for Metadata API, also SOAP APIs3 votes -
Allow optional parameters to the GearSet login url to support login method and custom domains if needed
When using Salesforce logins along with a custom domain, the current gearset login process requires 6 steps:
- go to https://gearset.com/
- Click "Log in" in upper right
- On the "Welcome back screen", click "Salesforce (Production, Developer)"
- On the Salesforce Login page, click "Use Custom Domain"
- Enter "customdomain" and click "Continue"
- Enter Salesforce Production Username and Password
If the GearSet login URL (from step 2) https://app.gearset.com allowed for optional parameters, a couple of the above steps could be eliminated
An example URL might be:
https://app.gearset.com?loginMethod=sfProdDev&customDomain=customDomain
or
Then that URL with the params could be saved as a favorite or placed in…
3 votes
- Don't see your idea?