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.
338 results found
-
Reward Systems That Reinforce Effort
When it comes to helping students stay focused and consistent, reward systems that reinforce effort can make a huge difference. Instead of only celebrating perfect scores, these systems highlight progress, persistence, and improvement. Whether it’s earning points for completing tasks, unlocking small incentives for consistent study habits, or receiving badges for personal milestones, effort-based rewards encourage learners to keep trying even when challenges arise. This approach supports healthier academic mindsets and boosts confidence over time. Many educators also integrate reflection activities to help students understand why their effort matters. By aligning rewards with growth rather than perfection, teachers can naturally…
1 vote -
1 vote
-
filter back propagation
Add an open pull requests filter for back-propagation PR's.
1 vote -
Provide a visual indicator on upstream systems when out of sync with master
Often times we see drift items added to PR's in our upstream systems. It would be nice to have an indicator that shows if a static branch is out of sync with master.
3 votes -
Add Marketing Cloud as an option for Compares and Deployments
Earlier this year there was a 'preview' option to allow for the Compare and Deploy features to interact with Salesforce Marketing Cloud orgs and business units. That option has gone away and I would love to have it back. As we support both CRM and Marketing Cloud it would be a great option to fold our Marketing Cloud configuration into our overall DevOps, especially around sending MC configuration and metadata to Github and different branches of a repository. In addition, it was going to be very helpful for moving configuration and metadata between different Business Units within a MC org…
1 vote -
How to Maintain Your Property After Bee Removal
After a professional bee removal, maintaining your property is key to preventing future infestations. First, inspect and seal entry points such as cracks, vents, and gaps in walls or roofs to keep bees and other pests out. Regularly clean the area where the hive was removed, removing leftover honey, wax, and debris, which can attract new colonies. Trim overgrown trees and shrubs near your home, as these can serve as nesting sites. Consider planting bee-resistant flowers if you want to reduce activity close to your property while still supporting pollinators elsewhere. Lastly, schedule routine inspections with trusted experts—choosing a reliable …
1 vote -
Mistakes to Avoid When Selecting a Mobile App Development Company
Choosing the right Best mobile app development company can make or break your project, yet many businesses overlook crucial factors. A common mistake is focusing solely on price—cheaper options often sacrifice quality, communication, and long-term reliability. Another issue is failing to review the company’s portfolio; past work reveals their design style, technical skills, and ability to handle complex features. Many clients also skip checking client reviews or testimonials, which can expose red flags early. Additionally, not discussing post-launch support can lead to unnecessary hassles later. Always prioritize transparency, clear timelines, and a team that understands your business goals to ensure…
1 vote -
1 vote
-
Pick up test classes to run from the apex class
Add a variable in apex classes where we can specify which test classes to run.
Recently you added the ability to specify the test classes to run on a pull request, which is great!
I know <ApexClassName>Test are automatically picked up by GS, but would be great if we could specify with
@TestClasses('CaseTestSuite,LeadTestSuite') or similar in the actual Apex Class and Gearset would automatically pick it up and add those test classes to the pull requests .3 votes -
AI-generated PR descriptions are availble only while creating PR and these descriptions are not currently present in the Pipeline UI , Can
AI-generated PR descriptions are availble only while creating PR and these descriptions are not currently present in the Pipeline UI , Can someone please look into this and it's good if we bring that changes as well to the UI.
1 vote -
Enable the ability to use Capturing Groups as part of the replacement in Environment Variables when using Regex
Twice now we have run into issues with deployments that would be satisfied by having the ability to use the capturing groups of the Regex expression in the Environment Variable to populate parts of the replacement.
A good example of this is usernames in Assignment Rules. Salesforce exports the assignment rule metadata from a developer sandbox without the sandbox name on the end. So, in the metadata file it has user@domain.com instead of user@domain.com.sbx.
In criteria you can also be filtering on email addresses, so if you just look for @domain.com in the environment variable, it will also find…
1 vote -
Remove "No Difference" items when commenting on jira tickets
when i connect a jira ticket to a commit, I like the way gearset posts a comment on the jira ticket listing the changed items. what I dont like is the long list of "no difference" items posted on the ticket. It makes the ticket comments super long and annoying to scroll through. can gearset update this to only post the difference metadatas, or at least give us the option to include or exclude
10 votes -
Automate upstream branch syncing
After merging/deploying to prod allow auto-creation of sync PR's to upstream branches/orgs (QA, UAT, Staging, etc...). If the sync PR's could be promoted automatically that would be amazing.
2 votes -
Add Pipeline Functionality to Handle Environment Refreshes and Branch Realignment
In many Salesforce development workflows, environments (especially static ones like UAT or SIT) are periodically refreshed from production. When this happens, the environment’s metadata and configuration can become out of sync with the branch linked in Gearset Pipelines.
This especially occurs when:
- Changes were made directly in production that didn’t flow through the pipeline, but now exist in the refreshed sandbox.
- A deployment was started partway through the pipeline but never completed to production, leaving partial changes held on branches in the repo.
Currently, the workaround is to manually run a comparison and commit the differences to realign the branch.…
1 vote -
Delete Flow by Version Number
It would be beneficial to delete specific inactive flow versions. Examples where this would help streamline deployment changes:
You need to delete a custom field that is used in a flow. You create a new version of a flow, remove the dependency on the custom field and activate the new flow. Now you want to remove the flow version that still has the custom field dependency. Something like a checkbox to select the version(s) to remove.
You have inactive versions of a flow and you want to clean up the historic flow versions. Something like a checkbox to select the…
2 votes -
I would like to suggest a feature for Gearset that provides a more granular control over user permissions. Specifically, it would be benefic
I would like to suggest a feature for Gearset that provides a more granular control over user permissions. Specifically, it would be beneficial to have the option to allow a user to commit changes to a branch but block their ability to create a pull request (PR). This would allow our team to review the commits before a PR is opened, providing a more effective way to manage and correct any potential issues before they impact the main repository. This is an improvement that would significantly streamline our workflow and reduce the risk of errors.
1 vote -
Restore feature branch when a mid-flight promotion branch is restored
Have just experienced a scenario where closing a PR that is mid-flight in the pipeline caused the promotion branch and underlying feature branch to be deleted. So far, so good in terms of expected behaviour due to my pipeline settings. However, after restoring the promotion branch in order to reopen the PR and promote it in the pipeline, the next environment on the pipeline did not then show the change. This, I believe, was because restoring the promotion branch DID NOT restore the feature branch. Therefore there was no source to create a new promotion branch from in order to…
1 vote -
Create a mass back propagation button
Its very time consuming to have to back propagate one by one to each org. Please create a mass back propagation button.
Also when back propagating where more than one connection to an org exists for instance our techdebt org has several admin connections and I have to hit update on all of them. Make the back propagation smart enough to know that it only needs one update rather than on each connection to the same org
1 vote -
Make pre/post deployment steps conditional on developer sandboxes.
Pre/Post deployment notes can be set to pertains to various static environments but they always apply to sandboxes after a back deploy. This should be conditional-- most of the time I only set them applicable to prod and they aren't applicable to developer sandboxes.
5 votes -
Ability to "Hide" Sandbox Groups on Pipeline Page
In the Pipelines page, it would be very helpful if we had the ability to "hide" entire sandbox groups from view. This would make it much easier to quickly find and focus on the environments that are relevant to the logged-in user.
Ideally, this "hidden group" setting would persist across logins and page refreshes, similar to how the "collapse group" feature currently works.
I'm sure an "unhide groups" feature will be needed with this as well, in case a previously hidden group becomes relevant again.
1 vote
- Don't see your idea?