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.
1301 results found
-
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
-
Automatically identify and run unit tests for deployed classes
When deploying, we have standard options for running tests. It would be great, if we have an option for "auto-specified tests" where Gearset would automatically find test classes for classed being deployed.
It can be done that in Setup, the team will define what type of extension the test classes has and then Gearset would use that key to find matching test classes.
E.g. we have the class "AccountServices" and we have developed a standard set that the test class has extension "Test", so "AccountServicesTest". In the Gearset setup we would set the variable for tests to "Test".1 vote -
Create a persistent default setting for Monitoring Job Notifications
It would be nice if there was a way to default the notification for monitoring jobs to 'send notification only when changed'. Right now, if you set monitoring, you get an email a day from that job, regardless if there was a change or not. You have to manually change it otherwise.
Nice to have that setting front and center, available when you select monitoring, as well as have a default value for each org type; Prod, Sand, and Dev.
2 votes -
Ability to modify pieces of data before deployment of data
E.g when you want to move data from PROD to DEV there are some fields (e.g. Contract Status) that you want to move from Active to Draft. This should be a generic function also to be applied to other fields / objects.
1 vote -
Custom ordering option for CI Dashboard
Rather than splitting jobs into Validate and Deploy and ordering alphabetically, allow custom ordering (drag and drop, or custom grouping) in order to maintain logical job sequences including a mix of deploy and validate jobs.
3 votes -
Display Deployment Status Progress
In the past in Gearset, you were able to see the status of your deployment (e.g. 100/200 test classes, etc.) very similar to how you would see the native status tracker on the Deployment Status page within Salesforce Setup. It appears this feature is no longer available in Gearset and there is no status until the deployment complete. It would be great to bring this back to Gearset, so the tool provides the full deployment scope. Since this has been removed, I now have to open an additional page to monitor progress in Salesforce.
10 votes -
Set values on record creation for fields that can't be updated
Some objects, for example PriceBook Entry, must have their attributes set on insert as once created most of the record is not updatable, e.g. CurrencyISOCode cannot be changed on this record once it has been inserted. Providing a way to set these fields on creation, rather than a later update step, would allow these records to be deployed as currently PriceBook Entry records fail in multi-currency orgs as they are all created with the default currency causing SF to treat them as duplicates
2 votes -
Launch into our Connected Organizations from various screens in Gearset tooling.
Since we have orgs setup in the Monitoring Dashboard or simply in the list of Organizations under My Connections can we get a button that can open that org in a different browser tab ... it would be a super usefuil feature for those of us monitoring many many orgs. its like SFDX ORG : OPEN -u alias name .,..... but having that ability in the GS Tools in relevant areas ... (Monitoring, or My Connections come to mind first.) We have a mixture of DEV, Production and other scratch orgs both internal and External Clients ..... its not always…
1 vote
- Don't see your idea?