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.
1306 results found
-
Unable to import/export translations using .stf file using greaset
Currently gearset allows to deploy translations from one org to another org, however we do not have an option to do the translations using .stf file /excel for the fisrt time in any one of the org
1 vote -
Make Data Deployments Invocable (Salesforce APEX)
As a feature to enhance data deployments, make them invocable by Salesforce APEX (or other tooling) whenever a Sandbox is refreshed. Salesforce has a configuration to let the user specify an APEX trigger/class to run upon Sandbox creation. That could call the data deployments to run on the freshly minted sandbox, seeding it with data. This would enhance automation.
There are tools out there (like SFApex) that do something similar.
1 vote -
add the ability to filter Git repos on connection
It would be useful to be able to select only applicable Git repos from source control that will interact with Gearset. A user may have many repos that they need on their account, but of those there may only be 1 which would be used via GearSet. It would be great if we could select which repos should be available when setting up the connection to our source control (specifically I am requesting GitHub but I think this would be useful for all source control integrations).
2 votes -
Display Permission Set changes as one entry
When working with Permission Set changes, it sometimes would be useful to see them grouped by Permission Set instead of being disaggregated by field. For example, we are migrating from using Profiles to Permission sets to grant all access. Currently, if we make changes to many (>100) fields in two different Permission Sets, we have to review many (>100) entries. Also, grouping by permission set would allow us to deploy changes to one Permission Set while ignoring the other.
2 votes -
Additional options for updating Azure DevOps work items
For example, we do not want to see messages posted for validation started, validation completed, deployment started, deployment completed. We only want to see messages posted on successful deployment. And one more thing is to update the State once the deployment completes successfully.
2 votes -
Add Analyzer to Warn/Remove Named Credentials with Passwords
Currently, attempting to deploy a named credential will fail as a "password is required for the specified authentication protocol".
This can mean manual work if you have a lot of CI deployment jobs to sandboxes or annoyance if you expected to be able to deploy it.
It'd be great if an analyzer existed that would alert/warn the user about it going to fail and unable to be deployed (suggest removing it from the package)
5 votes -
enable data deployment template merge
It is currently possible to select an existing template and add new objects and data deployment logic into it then save as a new template. It would save time to enable the selection of 2 existing templates and merge them into a single one.
1 vote -
Run all tests only when have apex classes in the package
Hello,
I want suggest an option to avoid run unit tests when no have apex class in the package.
And run all tests when have any apex class in the package.1 vote -
Modify files during deployment process
In Salesforce, if you add an image to a PathAssistant, it hard codes the sandbox URL in the metadata. This causes failures when you then try to deploy that item to the next environment. My idea is that a feature is added that would allow some sort of find/replace logic that's applied prior to the CI compare. Something like:
File: Enter the name of the package file
Search Text: The text and/or regex string to search the file for
Replacement Text: The text to replace found the text withIn this way, it would modify the source file prior to…
2 votes -
Need to have JIRA integration with Data Deployments
Need to have JIRA integration with Data Deployments which will improve the process and allign it with meta data deployments
1 vote -
Select a set of data deployment templates and run them in order
Ability to build sequence of data load (choose a list of data load templates and have to possibility to run them automatically in sequence). The sequence can be changed.
11 votes -
Allow bulk export of selected objects in selected historical data backups
It would be great to export all, or a selected timeframe, of data backups for a job. I understand this would be a large volume of data so selecting by object would be great.
For example, if there is a data backup for all objects that runs daily, I'd like to select the Account object and select a backup timeframe of 1/1/2020 - 12/31/2020 to export a .zip folder of 365 Account.csv files.
2 votes -
Scratch orgs with packages with InstallationKeys fails to install in CI
When creating a new scratch org you have the option of specifying the package and the installation key. This option is not available in a CI job to scratch org target scenario.
When there are dependencies specified in the sfdx-project.json file that requires an installation key the CI job run fails when the CI tries to install them.
There needs to be a way to specify the installation key, either by a custom JSON field in the sfdx-project.json, or on the CI job itself.
5 votes -
Publish dynamic data with Outgoing Webhook in CI deployment jobs
As of now we are able to send only static text as a part of outgoing payload in CI Integration jobs. We want this data to be dynamic for each deployment.
For example: We need to send the information like (JIRA User Story number, GIT commit hashes and descriptions from the pull requests being merged, etc.)
This will allow us to publish information of successful deployments to external system.20 votes -
Checkboxes to delete multiple packages/validations/deployments at a time
Hi - feature request:
Checkboxes on the validated packages (and probably others) screen so that I can delete validated packages more quickly. One by one is a big pain, and it probably uses your storage... and it definitely clutters our workspace.
Thanks!2 votes -
add static code analysis results to pull request
Can you add the ability to add the static code analysis results to a pull request? Or link back to the deployment summary screen with the results displayed there?
4 votes -
Hide irrelevant comparison types/components
After selecting the source org and viewing the metadata comparison filters, there should be an option to only show those types that contain data (the ones that have a number in parentheses). Or in other words... the ability to hide anything that isn't being used.
This would make it much faster to create new comparisons (or troubleshoot existing ones).
1 vote -
Add support for deploying a name change to a SFDC component (such as profile)
We occasionally change profile names during permssions clean-up projects. Currently, when you deploy a profile with a changed name, Gearset recognizes it as a "new" and a "deleted" profile, instead of a single "changed" component, which makes the deployment challenging.
I know that the name is used as an identifier, since the Id may not always match between source and target. However, if you add support for this, the tool could try to identify components with name changes by looking for the same Id in source and target with a changed name.
2 votes -
Inline Editing of metadata
Inline Editing of metadata
In order to make our deployment successful we had to download the package, modify the version numbers on the flow definitions, and then compare the local package to the target org. It would be very helpful if we can edit the metadata XML in the UI so we can fix the version numbers.107 votesHello. A large number of commenters requested the ability to carry out value replacements as part of metadata deployments.
Gearset now offers a feature called Environment Variables that lets you do just that!
It works with both manual and CI deployments and lets you target either a Salesforce org or a Git repo of your choice. And, for a number of key metadata types, you can even specify the exact 'field' where the replacement should take place.
If you have any feedback on the Environment Variables feature, please open a new feature request or simply let us know in the in-app chat.
Thank you for upvoting this feature request and we hope that you will find the Environment Variables feature useful.
Blog post: https://gearset.com/blog/environment-variables/
Support doc: https://docs.gearset.com/en/articles/5557015-using-environment-variables-in-gearset
-
Ability to use Sandbox Source Tracking features as opposed to a comparison filter
The comparison screen is great to help admins and declarative users see the changes they made. However, it still requires them to know which metadata to pull based on changes they made.
Source tracking in Sandboxes is in beta and would alleviate this concern.
https://help.salesforce.com/articleView?id=sfdx_setup_enable_source_tracking_sandboxes.htm&type=5
If Gearset could leverage this functionality (potentially leveraging SourceMember object or storing .jsons to track last modified times as local projects store) it would make the complete process easy to use for all alike (pull metadata, select diff, deploy).
5 votesWe’re currently working on a technical spike to incorporate source tracking capabilities into how we retrieve metadata. We’ll keep you updated on progress.
Regards,
The Gearset Team
- Don't see your idea?