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.
275 results found
-
Validation Job to validate feature/* branch by scratch org creation
The idea is to validate feature branches in repo. For doing this it's necessary to allow specifying source branch by pattern (like feature/*) in "Add CI validation job" menu. The validation should check whether the code breaks the scratch org creation or not. This is valuable due to fragility of scratch org creation process (sfdx force:source:push).
5 votes -
Allow export of code coverage results in daily Unit Testing job
It would be great to be able to export the list of unit tests and their respective code coverage in a csv file for further internal processing.
2 votes -
Bash scripting
Add support for bash scripting. This is one of the most powerful features of Jenkins and something that would make a huge difference in Gearset.
5 votes -
Allow orgs to be grouped in folders
On the “My Connections” page, I'd love to see an option to add a folder (and sub-folders).
Currently, there are options for "Developer orgs", "Sandbox orgs", "Production orgs", and "Scratch orgs".
If you are running more than one entity, having the sandboxes related to a single entity inside of a folder would be more user-friendly than having multiple dev/sandbox orgs inside the same folder.
For example, if I'm managing deployments for "ABC Company", "XYZ Company", and "LMNOP Company", and each has multiple sandboxes, it would be really convenient to be able to separate out their various sandboxes more effectively, into…
2 votes -
Users should be able to specify test classes and save them to draft deployments
Users should be able to specific and save test classes in the comparison stage so they can be saved in draft deployments. Seems like a waste of extra steps to unclick tests and select tests over and over as you work through a deploy.
also when deploys are combined, they would get all the test classes, again, saving lots of time.
6 votes -
Global Search feature
It would be very useful to have a Global Search feature within Gearset. This would be used to search the contents of all metadata objects.
My use case is that sometimes a string has been hardcoded inside a function. The only way to find the function that contains the string is to manually trace through the code. The global search would indicate the function that contains this string.
Another benefit would be to track dependencies for metadata objects that don't support dependency tracking. For example Aura Components, we could search for the component name.
11 votes -
1 vote
-
I would like the ability to change filtered metadata to their API names
I recently had an internal business conversation to clarify what would and wouldn't be included in our new CI/CD process leveraging gearset to push to orgs. When we had this conversation we used the Metadata API names to discuss and then when I went to implement it in Gearset I saw that the filters are actually some translated 'friendly' names.
This is of course fine for most use cases, but it made it really difficult to make sure nothing is being missed when setting up the CI/CD filter type.I would kindly ask that you implement some switch to allow…
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 -
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 -
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 -
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
-
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 -
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 -
Delegate access to a scratch org
The ability to delegate access to a scratch org without extending access to the related production environment would be helpful. We have situations where we need developers to build new ideas in a scratch org but do not want to extend the access to the production environment
1 vote -
1 vote
-
Create post deployment automations to SF records
Hi Gearset😍
Love your deployment product!We are using salesforce as a ticketing system - any chance you are planning to make a connection to Salesforce records like you did for Jira or Azure?
I would love the have the option to do some things automatically after a deployment, for example:
Attaching the deployment report to the ticket
Updating Status field
Update Environment Field (based on target org name)
Posting a chatter post about the deploymentThanks!
1 vote -
Mass delete of deployment and validation history
Would like the ability to delete multiple history items at once. The current process of clicking delete and then clicking the confirmation is cumbersome and time consuming when we have multiple users and multiple environments kicking off many CI validations through the day. Failure to clean up the Validation history, especially, eventually brings Gearset CI viewing to a crawl. Having the ability to delete multiple at once and/or a the ability to add a retention period for history would be ideal. Validation history is the most important because you can't filter by time period like you can when you go…
1 vote -
Clone deployment package from within the CI job history
We have a feature branch we create a PR 1 to SIT -> we merge the branch -> deploys to SIT -> we delete the branch
We have a feature branch we create a PR 2 to SIT -> we merge the branch -> deploys to SIT -> we delete the branch
now both PRs are in SIT branch
we make a PR from SIT to UAT -> Both PR's are validated against UAT -> if all is good both PR's get deployed to UAT
but then Monday comes and business wants JUST PR1 to be deployed to production
so…1 vote
- Don't see your idea?