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.
1240 results found
-
1 vote
-
Create post deployment automations to SF records
Hi Gearset😍
Love your deployment product!We are using salesforce as a ticketing system - any chance you are planning to make a connection to Salesforce records like you did for Jira or Azure?
I would love the have the option to do some things automatically after a deployment, for example:
Attaching the deployment report to the ticket
Updating Status field
Update Environment Field (based on target org name)
Posting a chatter post about the deploymentThanks!
1 vote -
Mass delete of deployment and validation history
Would like the ability to delete multiple history items at once. The current process of clicking delete and then clicking the confirmation is cumbersome and time consuming when we have multiple users and multiple environments kicking off many CI validations through the day. Failure to clean up the Validation history, especially, eventually brings Gearset CI viewing to a crawl. Having the ability to delete multiple at once and/or a the ability to add a retention period for history would be ideal. Validation history is the most important because you can't filter by time period like you can when you go…
1 vote -
Clone deployment package from within the CI job history
We have a feature branch we create a PR 1 to SIT -> we merge the branch -> deploys to SIT -> we delete the branch
We have a feature branch we create a PR 2 to SIT -> we merge the branch -> deploys to SIT -> we delete the branch
now both PRs are in SIT branch
we make a PR from SIT to UAT -> Both PR's are validated against UAT -> if all is good both PR's get deployed to UAT
but then Monday comes and business wants JUST PR1 to be deployed to production
so…1 vote -
Allow bulk export of selected objects in selected historical data backups
It would be great to export all, or a selected timeframe, of data backups for a job. I understand this would be a large volume of data so selecting by object would be great.
For example, if there is a data backup for all objects that runs daily, I'd like to select the Account object and select a backup timeframe of 1/1/2020 - 12/31/2020 to export a .zip folder of 365 Account.csv files.
1 vote -
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 -
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 -
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 -
Individual Assignment ruleEntry
Please Allow us to Deploy individual Assignment ruleEntry rather than the whole file/set, similar to components in other objects, sharing rules.
1 vote -
1 vote
-
1 vote
-
add the ability to change columns in the compare results page.
Use Case:
When deploying items from one Org to another I need to filter by newly created items as well as latest modified items. So there is a use case here to add the Created By and Created On columns in the Compare window.Or the ability to add predefined columns into the view.
1 vote -
Add a batch size option directly on Data Deployment and Data Templates
Currently we can specify the batch size for bulk data loads on Account level.
With this kind of setup we can't have two pararell jobs running on different batch sizes and we also need to memorize what batch size is required for each of my Data Templates.
It would be nice if we could do that directly on Data Deployment job and even save such setting in a Data Template.
1 vote -
'Select All' on Draft Deployments and Deployment History
When combining packages it would be very nice if there was a 'Select All' checkbox.
1 vote -
Jira ticket association should carry over to deployment merges and comparison refreshes
If I clone a deployment, it copies all the associated Jira tickets, but if I merge two deployments, the list of associated Jira tickets is empty. Is that how it is supposed to work? I would expect a union of the lists of all the merged deployments.
The same would apply to comparison refreshes.
1 vote -
WebStoreTemplate
Please add WebStoreTemplate as a metadata type
1 vote -
Jira: Ability to pass a list of Jira ticket Ids vs. single entry
Would really benefit from being able to paste a list of Jira Ids, e.g. comma-delimited (similar to specified tests) on final deployment. Hate giving up validation / deployment status writebacks to Jira, but often we have packages spanning dozens of Jira tickets and entry can be time-consuming, especially if there is a failure or refresh needed and Jira ticket associations get lost from the draft.
1 vote
- Don't see your idea?