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.
1357 results found
-
Support Email Template Folder metadata migration
Metadata API for EmailTemplateFolder does not accept wildcards so you have to know the name of the folder to be able to pull it down and migrate it. Currently (as of 2-16) the Gearset product cannot pull these.
Suggest that they add functionality to make a SOQL call to get all the folder names, at which point they should be able to pull them. Allowing for compare and deployment.
2 votes -
New Feature: Filter Custom Fields (and other sub-components) in Comparison Filters
I'd like to be able to exclude certain custom fields from my comparison.
For example we have fields that have environmental differences between orgs that we don't want to deploy. There are also random fields on standard objects that show up as "different" even though they aren't and it would be nice to filter them out.
4 votes -
Filter Column Sub-Levels
If I filter a column, it does not apply those filters if I open the sub-levels of an item such as "Depends on" or "Used by". For instance, if I filter OUT under the "Difference Type" column "No Difference," when I search through those sub-levels, it should not show me items that are "No difference."
2 votes -
Filter users for monitoring notifications
Hey,
Would be very beneficial if in monitoring tab, we could filter out users that we get the notifications about.
For example, we don't want to receive changes that changes have been made in a Salesforce org if these changes are a deployment, but we would be interested to see if any users with Setup permissions are making changes to fields, objects etc.
2 votes -
Add tool to send emails after deploying to specific targets
A project manager on my team expressed desire to receive reports when someone deploys to our production org. I would appreciate a tool that sends these emails only upon successful deployment to that specific org so that recipient's inbox is not flooded with every successful and failed deployment to every org.
2 votes -
Record/file level filters for Backup jobs
Allow Backup job filters to be configured for specific records/files rather than entire objects.
2 votes -
Create JIRA ticket when CI Job runs sucessfully
I undrestand that gearset can update status, comment and attach report to an existing JIRA ticket once a deployment is successful, but it would be nice to have a feature that would automatically create a JIRA ticket once the CI Job runs, and deployment is successful, for reporting and internal auditing
1 vote -
Ability to Template Scratch Org Settings
It would be great if it was possible to template the scratch org creation screen.
We have a lot of managed packages that need to be installed and having to enter the ID and Key every time is very time consuming.
1 vote -
Data deployments should ask if you want to Insert or Update or Insert & Update data
Data deployments should ask if you want to Insert or Update or Insert & Update data.
Currently it always performs data upsert only
1 vote -
It would great to be able to monitor certain user actions, such as exporting a report in Salesforce.
Right now, I am only aware of having to purchase an add-on from Salesforce to be able to get this information.
1 vote -
Allow retention policies to be set on individual core objects
It would be useful to be able to set individual retention policies on core objects, rather than on the entire backup job. This is for an old org (c.10 years), ideally you'd be able to set differing retention policies on different objects; e.g accounts after 7 years but contacts after 5 years.
3 votes -
Ability to recreate a reusable list or group for Deployment notifications
Every week we have a larger sized scheduled deployment for logic updates that runs after business hours. There's usually the same 2-6 people (often increasing) that want to receive an email and/or text message when the deployment succeeds. Whoever schedules the deployment has to add each one manually every time, and it would be nice to have a way to send notifications to a predefined list or group of email addresses and/or phone numbers.
It usually has to be the person that schedules the deployment, because if someone goes back to add their own email or phone to an already…
5 votes -
Meta Comparison Filter Based on User and/or Timeframe
It would be great if there was a way to create a metadata comparison filter, and not just filter with regard to metadata types, but also filter by which user made the change, or the timeframe when the change was made? For instance, it'd be great if I could create a filter based on changes I made within the past 30 days, or a specific timeframe. Filtering by metadata types takes very long for large orgs, even if I reduce the metadata types down to 1 or 2.
2 votes -
provide the ability to add tags to branches within Azure DevOps.
Within Azure Devops you can group commits and changes into a release based on a tag. So for a user to be able to add that tag when they are associating a workitem to a commit would mean they didn't have to go into Azure Devops later to add the tag.
3 votes -
Increase the size of the 'Create new branch from...' modal.
When creating a new branch from the 'Create new branch from...' model, it's hard because of the small size of the modal/dialog. Just sizing the modal/dialog larger would make it easier to work with.
1 vote -
Production/Sandbox Backup job color
The backup job color (or a colored tag) should be introduced so you can clearly see which backup job is for Production and which is for a Sandbox.
At the moment they all look the same and you have to make sure you are clicking on the correct one, only by looking at the username to understand if it is a Production org or not.
This is confusing and risky
2 votes -
Additional text countries
I'd like to see a few extra countries added to the text messaging option on scheduled deployments. My team works with resources in different regions.
Brazil +55
India +91
Philippines +631 vote -
Add the ability to report on validations and deployments via CI
Currently, it's not possible to see a report on when a validation or deployment started and ended for a given CI Job across multiple PR's. This will help understand how long on average validations or deployments are taking for a given environment.
1 vote -
Restrict visibility for monitoring jobs
I would like to be able to monitor daily changes made without those monitoring jobs being visible to the entire team. We have some super motivated people as well as the other end of that spectrum. I would like to have some data to visualize daily without the entire team seeing what I am doing.
2 votes -
Add to draft deployment as you build
Ideally I'd be able to add metadata to a draft from within salesforce - via a chrome addon maybe?
1 vote
- Don't see your idea?