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.
1354 results found
-
Show file storage backup progression
When having large SF orgs with large file storage amount, is impossible to see the progression on the backup. You can only see the object that's being processed. For our org we've seen "Attachments" object under backup for more than 1 month without any idea on where we were.
It would be really helpful to have information on the progression of each backup object (either data or file storage).
Showing the information like: "Backing up file storage in 'Attachments' (1/12). Retrieving record XX of a total of XXX records from Salesforce". Already backed up XX GB in file storage.1 vote -
Update the layout comparison view of Page layouts to reflect custom button/button changes on related lists. Currently XML view only
The layout view does not show custom buttons added to related list/other button changes. This is visible in XML view, the layout view is slightly confusing as a result - The "Select all" tick at the top is present, but no other tick boxes, making it unclear what you are selecting unless you use XML view
1 vote -
Date to date filter
A date to date filter so as to ignore anything outside of that time window. Even if it could just be all the changes for one year, that would help.
1 vote -
Allow a PR template from GitHub to pre-populate the PR description
There is a feature in GitHub to auto-populate the PR description (forcing, for example, a checklist if using the web UI). If Gearset could read that template and pre-populate the PR description so users have to put in specific comments (such as manual steps to be done after deployment) and if that description were exposed in GitHub, then it would be more seamless and the deployment history would enable an admin to work through each manual step without looking in closed PRs in Gearset.
2 votes -
Create ListViews in the Continuous Integration Dashboard
Create ListViews in the Continuous Integration Dashboard page and being able to grant access to specific users or groups of users.
The idea is to avoid displaying specific jobs to a particular group of users for better organization and reduce the loading time when many CI jobs are configured.
3 votes -
Allow different source control users per CI job
At the moment, my GitHub user is defined at an account level. So that user is the one for all CI jobs.
I may want to have a different GitHub user for each of the projects that I run through Gearset. For example, if we are a consultancy that generally use our own stack, but have to use a GitHub user belonging to a customer on some occasions.
Or (as I do now) I may want to switch my GitHub user from one to another. Today, switching that user will disable ALL OF THE CI JOBS. And I will have…
1 vote -
Add the option to schedule weekly, monthly and yearly backups
To meet our backup compliance requirements I'd like to suggest an option to schedule weekly, monthly, and yearly backups to go along with the daily backup option that is currently available. This way, we could setup multiple backup tasks with different retention.
Thanks
6 votes -
Save Filtered Metadata from a Comparison View as a New Custom Filter
When running a compare, we'll often filter the list of metadata types in the results to eliminate types we're not interested in comparing. It would be nice to save the filtered view as a new Metadata Filter for use in a future compare.
2 votes -
Enable Field Level Mapping for Data Deployments
Currently there is no field mapping option available for Data Deployment of Objects. This is a big blocker if we want to migrate selective fields data across Salesforce instances.
19 votes -
package missing -meta.xml endings
When I download a package from a CI Job, it doesn't include the require "-meta.xml" ending for my metadata types. I wrote the following script to add them back one folder at a time. It would make more sense if Gearset just gave me the correct filenames when I download the package though.
…# Gearset gives us a downloadable package to trouble shoot, # but it doesn't have the -meta.xml text appended to it. # Find all files with this ending and append -meta.xml to it. find ./ -type f -name '*.flow' | xargs -I '{}' mv '{}' '{}'-meta.xml find1 vote -
Sandbox Deployment With 0 Components
Running a deployment into a Sandbox or Prod that has 0 components is a waste of time and resources.
If a deployment has 0 components in it, either
1. There's a problem because I was expecting greater than zero (so throw an error), or...
2. I want to run tests, and theres a different command for that (I shouldn't be executing a deployment just to run tests).3 votes -
Button for 'All the Differences' that gives all additions, deletions, and changes
I'd love to have a button for 'all the things' (new, changed, and deleted). Currently, every time I run a compare, I use the All button and then turn off 'No Difference' on type.
4 votes -
Ability to assign Data Deployment Entitlement through Shared Connections
We have a central Gearset Owner who setup our various orgs using a dedicated Integration User in each org. They then shared the connections with Gearset Users so the credentials remain hidden.
However, this only delegates metadata deployment entitlement, not data deployment. To allow data deployment, a User needs to remove the shared connection and set up the org connection themselves.
Data Deployment Entitlement should be managed as part of the shared connection, as well as Metadata Deployment Entitlement. This will maintain the ability for central management and also keep org credentials secure.
5 votes -
Validation job when PRs are raised
Requirement :
Provide option to create a CI Validation Job only with "Validate pull requests targeting the source branch" and keep "Run Job" dropdown as optional .As Of Now :
When we raise a PR, it initiates feature branch validation ( cos, we enabled "Validate pull requests targeting the source branch" ), and after that when we merge feature-branch to target branch, it re-initiates another validation job.
For us, it's like similar validation is running twice on different events from which we can't opt out.Pros :
We can handle when to validate a feature branch, instead of bundling…
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…
3 votes -
Ability to delete app visibility
As per the official reply from Gearset support
".....The issue is, if you manually delete the app, all the app visibilities will be deleted as well. But when using Gearset to delete the app visibilities, they are not completely deleted but set to false. The best workaround for this is to manually delete the xml from your git branch. ..."
If Gearset can incorporate this feature, it would be nice.
The workaround is not that hard as it may sound. 4 apps in 60 profiles takes about 10 mins to mass-find and mass-replace in VS Code.
1 vote -
Make filter to search through all the components which are hidden under 1st level and expand the components
Can I ask Gearset team to add filter in compared components to search through all the components which are hidden under 1st level (e.g. custom objects or profiles).
For example, in the filter to compare metadata I selected certain custom tab (in the profile the access to the tab was deleted), also selected certain profiles, but serching through the compared metadata list I spent hours and did not manage to find those components for deployment package.
The same is for object access. I selected certain object, selected certain profiles - and again, it's a hard quest to find necessary components…3 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.
2 votes -
Backup data search feature should allow wildcards
Current the backup/restore search feature is an exact match search only. It would be great to use wild cards or to select "contains" "starts with" "ends with" or simply allow the user to use % to achieve the same.
For example if I wanted to search for the account Willy Wonky Chocolate Factory, with the exact match I have to know the exact name, but with wild card I could search for %Chocolate% and get all accounts backed up with Chocolate in their name.
1 vote -
Write Deployment Results back to the user's Salesforce org
When setting up a deployment, it would be helpful to capture Deployment Results in a custom object in the running user's Salesforce org. Users would be able to specify a unique reference at the point of deployment, which would track through to the Salesforce org.
Information about the deployment would be captured in a Master record, with data about individual components existing in Detail records.
Org admins would then be free to leverage automation features to map the created records as they see fit.
As a consultancy that tracks our customer requirements in Salesforce, our use case would be that…
14 votes
- Don't see your idea?