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.
1309 results found
-
Add feature for admin to disable all email notifications globally from the profile
Add feature for admin to disable all email notifications globally from the profile
1 vote -
Show expired orgs in list of salesforce orgs
When checking my list of salesforce orgs it would be good to see that the listed orgs have valid tokens and if they don't have valid tokens either checked on the fly/daily etc or just from previous automation attemps/backup attempts this would really help when you have access to many sandbox orgs on your user account.
https://i.imgur.com/j0qb4Bq.png Example possible implementation?1 vote -
Include Apex classes regardless of folder
In GitHub, Apex classes don't always have to be in a folder called "classes " to work with them. Some people using SFDX put test classes in their own folder (sometimes called "tests". Even Apex classes within the "classes" folder can be sub-grouped into folders. (Example at https://github.com/trailheadapps/apex-recipes/tree/main/force-app/main/default/classes)
I'd like Gearset to scan the entire repository and to group metadata by its actual type, not by the folder it is in.
I'm not talking about the sfdx-project.json saying where the metadata is located. This is within each of those locations, it should find all Apex (for example). The Apex…1 vote -
Support Filter by Status from Monitoring History
I occasionally need to review the Monitoring History for a particular org over a period of more than a few days (eg. Last 30 Days or more). I'm only interested in reviewing entries where the Status = "Different" so I can quickly ignore those that are "Identical". This would be a good place for a column filter like those that you support on the Compare & Deploy page.
It would also be nice to have the ability to filter on other columns (eg. Changed, New, Deleted, etc.) like only those entries where New components were added.
Thanks in advance!
1 vote -
Page layout comparison in Same Org
It would be so valuable and help immensely with tech debt to be able to compare page layouts and lightning page layouts within an org to see what the differences are.
1 vote -
dynamic search function after comparison
dynamic search function
it would be helpful after the comparison to look for multiple components at the same time and not each one individually. for the release we get a list of components example from the developer:
CustomerAddress
CustomerNamec
Customer_Telc
...I want to include the entire list in one search, and I want gerset to search for each row individually. Example in SQL:
SELECT * FROM table
WHERE column1 LIKE '%customeraddress%'
OR column1 LIKE '%customernamec%'
OR column1 LIKE '%customer_telec%'
OR column1 LIKE '%customertele_c%'
...this change would save us…
1 vote -
Integrate with Rally as an option in addition to JIRA/ADO
We have customers who use Rally to manage their requirements similar to how many use Jira. Would be great to have this capability
1 vote -
Retrieve Metadata into local environment (e.g. using VSCode pluging)
This would make the integration of Version Control and Gearset nicer. Where now user has to go to Gearset deploy to a feature branch, afterwards, go to VSCode pull from the feature branch.
1 vote -
Rolling back deployment made by CI JOB
Currently it is possible to roll back a deployment made by CI Job, though that rollback will only be performed to the specified Org. Hence, other Orgs have to be rolled back individually.
Use case: I have propagated changed from my Sandbox to Staging. An issue was identified that requires a substantial amount of work where that feature cannot be included in the next deployment to production, hence it needs to be removed from Staging. Though, other sandboxes back propagated that feature because they assumed it should work.
It would be amazing if the rollback used Github commits, so the…
1 vote -
Remove/Deactivate new feature for batch comparison
A few weeks ago, Gearset added a new feature to officially make the comparison faster, by showing already results of first batch and add the rest later on.
This feature makes it much more difficult to do comparisons. First of all, I don't see any benefit. I still need to wait for the whole comparison to finish, because I still need to now, what has changed. Why should I look into the first things, when I need to look into it again, after the rest is compared. So before I can select anything, I need to wait the whole time…
1 vote -
Add More Granular Control over Email Notifications
Allow users to enable/disable categories of email notifications at the user level. E.g. success emails for monitoring jobs, deploy succeeded/failed emails, etc.
Alternatively, or possibly in addition, allow users to "mass-edit" job notification settings, so we don't have to edit each one individually.
1 vote -
UI Change: On any pop-up page using Source Control, auto-expand to show Create Branch button
On a monitor job (and probably elsewhere), clicking "Deploy To" and then selecting Version Control target, you get a default branch, typically master. If you click the link to Create a new Branch from Master - you input the name of your new branch, but the Create Branch button is hidden below the display and you need to scroll down to show it. The Start Comparison button is where the Create Branch button should be, so you end up starting your comparison instead of creating the branch first. Suggesting to change the pop-out window to expand to show both buttons…
1 vote -
Show Formula Comparisons line by line
When comparing formulas (in validations, formula fields, workflow criteria...) the comparison should be done line by line.
Considering the whole formula a block and only showing that "something" has changed in the formula is not useful when looking for conflicts between environments.
When pushing changes between environments, admins are checking to make sure they are not overwriting other changes with their update. They most probably know the formula has changed (that was their job) but they need to ensure no unwanted changes are added/deleted from the target environment.
In long formulas with many lines (potentially >100) it's not easy to…
1 vote -
Unify the message when you authenticate an org with a username that has been shared. It uses the term "delegated" instead of "shared"
Unify the message when you authenticate an org with a username that has been shared. It uses the term "delegated" instead of "shared". This could be confusing.
1 vote -
Sort Validation Only CI Jobs
In the CI Job page, you can sort the top-level jobs by different columns (Job Name, Source, Target, etc...) but you can't sort the actual instances of that job.
We can get up to 30 PRs that are all being validated, and it would be nice to be able to sort them in some controllable way. It seems to rearrange them in whatever way it feels.1 vote -
Be Able to deploy Portal Sharing Settings and Organisation Wider Default Sharing Settings at the same time
For example if attempting to deploy
OWD permission Read -> Private, and Portal Sharing Set None -> Read. Gearset will fail validation due to SF complaining that Portal Sharing Settings cannot grant Read permission, since OWD is already giving that access.
Though what SF sees is that Portal Sharing Set is trying to give Read when it already has that access.Therefore, if I want to make the deployment then I would have to do in 2 steps.
1 vote -
Allow Data Deployment to handle more complex structures
Currently, user is able to select Obj A, Obj B that references Obj A, Obj C that references Obj B. And, in the next step of data deployment it allows user to select Objects where Obj A, B or C, and objects references by those objects.
If we ignore above example, I want to be able to select: objA(id), objB(id, objA), objC(id, objB, objD), objD(Id), objE(Id, objD). Where the first object I select and everything else is filtered on is objA.
1 vote -
Activity Task Event field level security validation in Profile
Hi Gearset Team,
I would like to have a metadata validation for profile field level security involving Activity, Task, Event object as they are related to each other in Salesforce.
For example:
If we do a retrieve for Activity, Task, Event object along with profile. In the profile metadata it would specify this:
<fieldPermissions>
<editable>true</editable>
<field>Task.FieldX__c</field>
<readable>true</readable>
</fieldPermissions>However, if there were to be a mistake in the profile metadata and we commit them in version control it is detected as a 'new item' in Compare and Deploy
<fieldPermissions>
<editable>true</editable>
<field>Activity.FieldX__c</field>
<readable>true</readable>
</fieldPermissions>When we select this new changes and…
1 vote -
Warn if source version is greater than the version of the target org.
Often, salesforce will deploy the latest API version to sandbox orgs before production orgs. Therefore it's easy to use API version 55 in your sandbox and then get a failure message when you try to deploy it to your production org which is at version 54. Unfortunately, you have to start to validate your deploy before you get this message. This could be a pre-deployment issue that you can notified right away.
1 vote -
Provide a better error when "invalid or null picklist values" is thrown.
"invalid or null picklist values" is thrown and i have too many picklists to figure out which one is the issue. Please provide speicific fields that are causing errors.
1 vote
- Don't see your idea?