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.
1235 results found
-
Lessen Permissions Needed To Run Monitor
When running Monitor, a user needs to have "Modify All Data" or "Modify Metadata Through Metadata API" permissions, and "Author Apex" is further needed if we want to monitor Apex classes. I understand why an user would need these when comparing for a deployment, but for a more "read-only" use case like running Monitor, is it possible to lessen the permissions needed?
Context: we're looking into using Gearset for auditing purposes, and the Monitor feature looks to fit our needs; that said, if in order to monitor production changes requires the user to have full deployment permissions (and author apex),…
1 vote -
Add Apex Page Permissions to Repo Dependency Cleaner Functionality
It seems based on the below doc
https://docs.gearset.com/en/articles/3624846-what-does-gearset-s-repo-dependency-cleaner-do
That the repo cleaner will remove permission references related to the following deleted items:
Apex Classes
Tabs
Apps
Object Permissions
Field PermissionsMissing from that list is Apex Pages. It'd be great to have that included to clean up references to the deleted page without having to re-run a 2nd comparison for source control.
1 vote -
export deleted data records in CSV format
We can currently view deleted/removed data records in XML format as a list, but we can't export them into a CSV. This is necessary people who don't have access to Gearset and would be very helpful for users who have difficulty understanding XML.
4 votes -
Allow custom manipulations to data during a data deployment
Export the selected data source in a CSV file before deploying, in order to allow custom manipulation. Then allow the import of that CSV to destination - functioning like a more sophisticated Data loader.
3 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 -
Control When Tests are Ran Based on Metadata type
It would be nice to control when we want tests to run based on the type of changes in the triggering event for CI. Something like only run test classes on update of Apex Classes, Flows, Workflows, and Objects.
This is a bit of a patch for not having test classes fully optimized but would be helpful with orgs who have lots of profile and layout changes.3 votes -
Allow searching Monitoring of a system by a specific record of metadata to see all the dates that the record changed
If I need to find when a specific thing was changed in our system, my only option is either to use the last edited date or to manually check every daily comparison from Monitoring to see if it changed. Since many metadata types do not reliably update the last edited date, it makes it much harder to find those changes. If I could choose a specific metadata record and use that to search the Monitoring to see when it changed, it would be much easier to find it.
9 votes -
Allow capability of excluding IP ranges from Profiles during migration
Currently IP ranges defined in, say, a sandbox get carried over to the target environment (another sandbox or Production), when Profiles are migrated.
In some cases this means, these means these IP ranges may have to be manually removed from the target environment.
It would be great, if there were an option to exclude these IP ranges from the selected Profiles.1 vote -
Allow Source to choose multiple Branch for CICD Validate/Deploy
when choosing source as GitHub it allows user to choose feature/*** which allows every commit on branch name starts feature will trigger the CICD
2 votes -
More granular permission settings for sub groups of a large team
Giving team owners/leaders the ability to define sub groups of team members and control their ability to deploy to certain environments.
For example not being able to connect to/make deployments to 'production' orgs.10 votes -
OAuth support for outgoing webhooks
Currently outgoing webhooks support only basic authentication. It'd be useful to have oAuth support for outgoing webhooks for enhanced security.
5 votes -
Sort Deployment Details by New, Changed, Deleted
Currently, it seems that the list of Deployment Details provided in Successful Deployment reports is sorted alphabetically by metadata type.
It would be easier to understand the impact of the deployment if the list was sorted first by category (Changed, New, Deleted, No Difference) and then secondly by metadata type within each category.
1 vote -
Control in which country data backups are stored or alternatively export backups automatically..
We require the ability to control where our data is stored. At the moment we need our Swiss backup data to be stored on Swiss servers. If this isn't possible it would be great if we can automatically export data via an API endpoint to our Swiss server.
1 vote -
Add the ability to restrict the Jira Projects Gearset can access
A Jira account may be linked to many projects which will never be interacted with through Gearset. However those projects might still be legitimate for the user, so they can change their project access on the Jira side. It would be great if we could select projects in the connection that we want to choose from when associating to a Jira item.
1 vote -
To be able to filter within a dropdown
https://ej2.syncfusion.com/vue/documentation/drop-down-list/filtering/
Much like the above, when searching through many fields it can be tedious1 vote -
Ability to merge the pull request from inside gearset. It gives me option to stay in one tool and carry out all my opertions.
In Gearset we have option to raise the pull request but we cant approve merge them inside gearset. There should be a checkbox which if checked should go and merge that pull request. That will allow the user to stay in one screen/one tool i.e. gearset. If someone wants to keep its approval processes in bitbucket then checkbox will allow them to only raise pull request and not auto merge/approve.
4 votes -
Manage multiple Gearset teams from a single Gearset account
I want to be able to manage multiple Gearset teams from a single Gearset account, and not have to log out and log in again.
17 votes -
Load Balancer for CI validation
would be nice to have possibility to configure 1 source (git branch), but multiple targets (sandbox), so gearset would have some "load balancer", which would distribute the validations into sandboxes, which are not busy. Its taking too much time from developers to wait for their validations to finish.
4 votes -
Deploy on pull request creation
Currently is supported only validation on pull request creation. It would be great if we can also do deployment on pull request creation, not only on merge.
2 votes -
Show associated JIRA ticket in Validated Packages & Deployment History and Export
We would like to view the associated JIRA in both the Validated Packages and Deployed History pages. In addition, we would like to export the associated JIRA tickets in the Export History Excel report, found in the Deployment History page.
We link our Jira stories to our Production deployments and we would need a way to report on which ticket is linked to which deployment. Currently this is only available if users are diligent enough to also write the story number in the Friendly Name or Notes.
This would be an extremely useful feature especially for companies undergoing SOX Compliance…
3 votes
- Don't see your idea?