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.
1231 results found
-
Add configurable email reminders for scratch org expiration.
From Salesforce orgs and Dev Hubs, it would be great if there were a setting that would automatically send an email when a scratch org is approaching expiration. This could be configurable per Dev Hub, and would help prevent data loss at scratch org expiration.
1 vote -
backup expiration
For compliance purposes I'd like to request an option to list the data backup expiration date. We are able to choose how long to retain the backup, but I do not see a place that lists when the backup is set to expire.
4 votes -
Show the status of a CI deployment on the pull request
We use merge-based deployments, so whenever a Github pull request gets merged to /main, a CI deployment job fires that deploys the content of the PR to Production.
The issue is that at the moment all Merged PRs look the same, whether the deployment actually succeeded, or failed. There's no way to tell, or even to follow progress, unless we ask people to open the Gearset job and then look at the deployments for that job etc. which is quite a bit of a faff.
Validation jobs do display on the PR whether they passed or failed, the same feature…
1 vote -
Analyzer: Duplicate child relationship name detection
Use case -
target org has child object O lookup field F1 with childRelationship = Foo
source org has child object O lookup field F2 with childRelationship = FooIf you deploy, SFDC tells you that there is already a Child Relationship Foo on O
Analyzer could detect this and warn developer before deployment
3 votes -
Analyzer enhancement - detect missing ContentAsset in CustomApplication
Given this XML in CustomApplication
<CustomApplication xmlns="http://soap.sforce.com/2006/04/metadata">
<brand>
<headerColor>#0070D2</headerColor>
<logo>MyLogo</logo>
<logoVersion>1</logoVersion>
<shouldOverrideOrgTheme>false</shouldOverrideOrgTheme>
</brand>If user forgets to select Content Asset MyLogo, Analyzer should detect.
3 votes -
Manual button to refresh repository data
Multiple times in the past, my team has added new files to our git repository and Gearset dose not pick them up as existing in the repository when we do a comparison.
Select your git repo/branch as the source, select the sandbox you want as a destination, the comparison page says "fetching repositories", but it doesn't seem to actually pull the updated data from the branches. My comparison builds fail because the new file isn't included in the comparison. Gearset usually ends up picking them up in ~12 hours but it's a huge workflow blocker when a tool doesn't have…1 vote -
Option to download problem analyzer template
Option to download the problem analyzer template so users have an option to add it to the custom github actions scripts to run CI validations for their own delta comparisons.
1 vote -
'Continuous integration' menu item links (redirects) to Deployment Pipelines
When I click on 'Continuous integration' in the left menu it goes (redirects) to Deployment Pipelines (https://app.gearset.com/deployment-pipelines?pipelineId=xxx) by default since a week or so! 👎
I just want that menu item to keep on going to the 'Continuous integration dashboard' (https://app.gearset.com/continuous-integration).
What's in the name (of the menu item)! 😉1 vote -
Link to the Salesforce Validation in Progress from the Pipeline
When I deploy using the standard deploy interface, there is a link that allows me to view the deploy progress in Salesforce.
In pipelines, I would like this same feature. When a deploy has been running for a while, it's useful to know where it is in the process and a quick link would be quite nice.
2 votes -
Provide account owners ability to control and lock certain features for team
Currently, there are some settings that we would like to turn on or off for the entire team. For example, the "Append Validation/Deployment items to ticket" toggles when doing a deployment. It is also unclear that when a team member changes these, they are changing the setting for the entire team, which leads to inconsistent Jira tickets, as some list the components and some do not.
We would like the ability for account owners to control these settings for the team and lock their ability to be changed by team members.
4 votes -
Bring back the Suggested Fixes in Problem Analyzer to suggest permissions for fields when moving a new field.
Previously if you selected to migrate a field, Problem Analyzer would suggest the permissions. Now it only shows up on Warnings tab. This forces you to go back to the Comparison and individually find the permissions for each field. It should include these as Suggested Fixes. Additionally, if a field is listed as a Suggested Fix, the permissions for that field should be included as Suggested Fixes as well.
3 votes -
Make Custom Filters a Top-Level Menu Item
Filters are arguably the best part of gearset, especially with the support for RegEx. It is kind of a bummer that they are tucked away in a modal that can only be reached by clicking into a dropdown. Ideally you could just go to Hamburger > Metadata Deployments > Custom Filters and be routed to a dedicated page.
12 votes -
Add issues from the problem analyzer to the comparison list
When I find issues in the problem analyzer, if I accept them, they only add the things that I have selected, but I can't add any related elements without going back to the comparison.
For example, if I miss a custom field in the comparison, but the problem analyzer flags it, I don't have any way to add the permissions for that field.
Instead, I have to go back to the comparison and add that missed field and then it's related features (this is a big problem if the analyzer flags a number of issues).
Having a button in the…
4 votes -
Sort or Filter Active CI Jobs
Currently, there is no great way to filter out old/inactive CI jobs from the Active CI jobs. This poses a problem as there are situations where we have replaced CI jobs in the past, or created/disabled test jobs. Currently they clutter up the Continuous Integration Dashboard, but it would be nice if we could hide them so we don't have to delete them and lose their history.
1 vote -
Allow CI jobs to use the running users GitHub connection
At the moment CI jobs within the Pipeline use the CI owner's GitHub account for new branches and pull requests etc which is stopping the code reviewers process within GitHub from working currently.
Can we allow the integration within Pipelines to run on the promoting user's connection (i.e. so requests are shown with the running user and not CI Owner within GitHub) or allow a generic user to be set up instead to untie deployments from the CI owner GitHub connection within Gearset.
3 votes -
Ability to Filter Out Namespaced Metadata
I figured the best way to write this out was in the form of some sub-par user stories.
As a Salesforce Admin, I need the ability to do a comparison of two orgs/repos and have it show only non-namespaced metadata so that I can easily distinguish between things I own and manage vs what are from managed packages.
As a salesforce Admin, I want to be able to indicate that I want to hide all namespaced metadata while still being able to show custom fields I create on a namespaced object so that I can quickly deploy new custom fields.
…
3 votes -
allow selecting of specific picklist values when deploying changes to picklist fields
Essentially would like to be able to cherry pick the values for a picklist value that is being deployed from a lower sandbox. Basically what you did with Precision Layout deployment for page layouts. There are times when we do not want to deploy all of the new/different values for a picklist field.
6 votes -
link deployment to a salesforce case
The ability to link a Gearset deployment to a salesforce case record. If an org uses cases to track a bug or feature, this feature would close the loop from that case to the gearset deployment.
I understand that there is a post to chatter functionality but it would be nice to target a specific case for auditing purposes.
1 vote -
Provide and enforce branch naming conventions
Branches get all kinds of really stupid names over time. It would be nice if Gearset provided an option to template new branch names. For example when my users need to create a new feature branch for their user story, Gearset should prefix that branch with 'feature/'. When a release branch is created it should be prefixed as 'release/'. Bugfixes or Hotfixes could be bugfix/ or hotfix/.
Dictating naming conventions is unenforcable. Keeping branch names organized goes a long way to keeping the repository maintainable over long periods of time. Even if folks are well intentioned, git branches are case…
2 votes -
Rerun faild tests on the unit tests screen
It would be nice to be able to rerun just the failed tests with a separate button, when debugging scheduled tests
1 vote
- Don't see your idea?