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.
1244 results found
-
Export Object level and OWD (sharing settings) in permissions reports (in addition to the field-level)
Currently, the permission reporting feature only provides field-level permissions export to CSV for all Profiles and Permission Sets. This is a very small part of the overall security and sharing permissions model. Here are a couple of items that I recommend adding to the permission reporting as a starting point:
- Object-level permissions (read/create/edit/delete/view all/modify all) for Profiles and Permission Sets
- Sharing Settings (organization wide defaults) for all objects
In the future, it would be nice to have additional permissions from Profiles and Permission Sets available to export such as:
1. App assignments
2. Tab visibility
3. Apex classes
4. Visualforce…1 vote -
"Next" button on comparison page sometimes does not work
Sometimes, the "Next" button on the comparison page does not work. In the Developer Console I can see a 403 response from "POST https://app.gearset.com/api/static-code-analysis", traced to "raygun.js:2016".
In this case, I have to reload the comparison page.
This happens quite often (I estimate 1 in 5 times).
I don't think that it's a timeout issue (CSRF token or sth.), because just right now I only marked one file in the comparison list and wanted to proceed, and the button didn't work.
On other occasions, I spend a lot more minutes on the comparison page, and the button works perfectly.
…
1 vote -
Only see deployment history for Orgs you have access to
We would like to only see Deployment History for the Orgs we have access to. Our clients brought this up as a concern during our deployment meetings.
1 vote -
Enable Dependency Cleaner only jobs on Git repos
Similar to Unit Test jobs for connected Salesforce orgs, it would be great to have independent Dependency Cleaner jobs for our source repos to help identify problems separate from any particular commit.
In our flow, not every commit goes through Gearset, so it's possible that our repo could become "undeployable" as a result of these non-Gearset commits. If this occurs, it then comes confusing on the next Gearset commit since the Dependency Cleaner will add all the deletions it deems required which don't relate at all to the PR being reviewed.
A the end of the day, we'd like our…
3 votes -
Don't change the first 2 rows of a metadata file in version control
Usually a Metadata file retrieved from Salesforce starts like this:
<?xml version="1.0" encoding="UTF-8"?>
<PermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">So two lines, first with the version and encoding UTF-8 and second with the type of metadata.
Now when GearSet does the deployment to version control, either from an Org or a Branch it uses this styling of the first row:
<?xml version="1.0" encoding="utf-8"?><PermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">
So everything on one line, with the encoding in lower case.
I don't see a logical reason this should be different in the files and is then causing differences in the version control system.
Thanks for looking into this.6 votes -
Yearly report of all previously migrated items.
It would be great to get an end of year report or report of how many migrations were completed and a high-level list of components.
Example:
Custom metadata, lightning components, page layouts, fields, apex, etc.1 vote -
Show Read Only Source control Settings to Members
Would be good to see the current settings of Source control for Members in read only mode.
Currently what greats us is just a text message:
"Only team owners can change these settings."1 vote -
Include the local file name on all the results screens
When you choose a local file to use as compare, on every subsequent screen the only title you see is: "On-disk repository". It would be helpful to include the name of the file.
1 vote -
Include the local file name on all the results screens
When you choose a local file to use as compare, on every subsequent screen the only title you see is: "On-disk repository". It would be helpful to include the name of the file.
1 vote -
Create Scratch Org dialog should echo DevHub name
When you Create a Scratch Org, the dialog that appears doesn't echo the DevHub name used to associate the scratch org. Since one's Gearset user account could be authorized to multiple DevHubs, one loses the thread (breadcrumb) to which DevHub is being used for the new scratch org
1 vote -
Add NotificationTypeConfig metadata type
There is a new metadata type in API 48.0 NotificationTypeConfig. It would be great if you can add it.
https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_notificationtypeconfig.htm1 vote -
Allow outgoing webhook option to be configured for Compare and Deploy
I need the option to configure an outgoing webhook when deploying via 'Compare and Deploy' feature. Currently webhooks are only available with the CI jobs.
3 votes -
3 votes
-
Move Package Contents to Left Column on Deployment Screen
On the "Summary of Items to deploy" page, the items in the deployment show in the 3rd column. So when you go to choose tests, you can't see what's in your package. Makes it very easy to miss a test.
Illustration: https://imgur.com/a/wbZOeiZ
1 vote -
inform users they're logged in somewhere else when failing concurrent logins
When a user might attempt to log into their account from a second computer (or VM), its appropriate to fail their login on the second computer. Right now, there is no indication that this has occurred because they're already logged in elsewhere. The error talks about adding Gearset IPs to Salesforce, but the issue is being logged in already.
I suggest telling us we're already logged in. It's easy to forget!
Thanks!
1 vote -
Filter branches by tag name
In order to remove the clutter when selecting a branch to deploy to or from, allow users to apply metadata filters that dictate which branches show up in Gearset. For example, being able to specify that I only want to see feature branches.
2 votes -
Searching for work item should allow for searching by ticket #
When searching for work items to associate to a deployment, user should be able to enter ticket IDs rather then key words from the Azure DevOps ticket title. This will make it easier to search larger backlogs.
2 votes -
Excluding Record Type Problem Analyzer Should Behave the Same Across Metadata (Layout Permissions, Custom Object Permissions)
In the situation where a repository is the source and an org is the target, there may be a situation where a record type doesn't exist in the repository but references in the layout permissions and custom object permissions do still exist.
Currently, the problem analyzer will catch the custom object permissions and ask you to remove the references to the record type that doesn't exist in the target.
However, it doesn't catch the layout permissions and the deployment could fail with an invalid reference.
In the absence of the record type in the repository, the "Problem Analyzer for excluding…
1 vote -
Schedule multiple gearset deployments
Have the ability to schedule metadata deployments along with data deployments. As of now, you must deploy all metadata then move into data deployments. It would be great to schedule these items in some sort of task flow.
2 votes -
Exclude specific Classes from Scheduled Unit Tests
Some Testclasses only run successfully, when the Org is connected to a Backend Application. Usually sandboxes for Development are not connected to the Backend. These are the Orgs, that we need to watch. It would be useful to exclude specific Classes on specified Environments from being tested in scheduled Unit Tests.
10 votes
- Don't see your idea?