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.
100 results found
-
Add a Description field in the General Settings for Automation like Continuous Integration.
We LOVE Gearset. I just took over when an employee on my team moved to a different team. I was looking over the existing Monitoring jobs and had to ask why some of them were setup. They were similar with the exception of when they run, for example. It would be helpful to have a Description field in the General settings section so when someone creates these jobs, they can give a brief description of their intent and purpose. Thanks.
1 vote -
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 -
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 -
Distinguish between process builder and flow
If you do deployments of flows and processes from process builder, both of them are handeled as a flow. If you need to activate the flow or process manually in a production org, you need to guess if it was a flow that you have deployed or a process.
Please within the deployment report (and the comparism), distinguish between flows and processes.2 votes -
Provide more detail in Monitoring notifications
Right now, the Monitoring job notifications (Slack especially) provide very little detail as to what actually changed.
Ideally, I'd be able to see right in the message (or in a threaded reply), the first X number of metadata changes made. If there are more than that, then providing a direct link to the detail page in Gearset would be great.
As of now, it simply just says "there were changes", with no detail or way to easily see the changes in Gearset...which is not terribly useful.
4 votes -
More custom monitoring delays
It would be brilliant to be able to choose the days of a week your monitor script runs on so I don't have to deploy changes every single morning and could instead do once a week
1 vote -
Filter deployment and comparison reporting by user in the account page
Right now Gearset is showing Total Deployment Team wise . My suggestion is to Publish User Wise Count of Deployments with all Successful , Failed Deployments .
1 vote -
Download metadata from monitoring job in SFDX format
Please add the opportunity to download the metadata from the monitoring and backup job in SFDX format.
1 vote -
Export test run history
Exporting the Test run history to Excel/CSV will allow keeping trends.
The ultimate goal is to include this in a dashboards. If an embedable web page could be generated with solely the trends, that would be perfect.
2 votes -
Email notification selection: none, success, failed deployemnts
In account settings allow me to choose what kind of notifications I want to receive to my email.
[ ] Send me success deployments notifications
[ ] Send me failed deployments notificationNo selection means do not send any notifications.
Why? With many deployments my email is bombarded with notifications. Last two weeks 65 emails which I do not read as I see status on screen. Therefore I want to turn off those notifications.
9 votes -
Attach pdf items details in the email notif "Your organization has changed"
When you receive a notification concerning a change into an organization you need to know quickly which items are changed.
4 votes -
On 'deployment' and 'draft deployment' pages provide a way to see the filter information without having to open the full comparison screen.
On 'deployment' and 'draft deployment' pages provide a way to see the filter information without having to open the full comparison screen. We need a quick way to make sure that item level filtering is being used on each metadata type
1 vote -
Ability to search Deployment History for specific metadata
On the "Deployment History" tab, the filter dialog filters on the visible friendly name and items like that. What I would like to do is enter a specific metadata name and have the list filter down to deployments where that specific metadata name was a part of the deployment. This would be useful when getting the question, "when was xyz last deployed?"
13 votesIf we implemented this and it was only able to search metadata from that point in time onwards, would that be useful or would it be confusing to communicate in the UI?
-
Allow searching for Org IDs in deployment history
Enable the search results in Deployment History to include Org Ids.
USE CASE: I want to see a history of all deployments into, or out of, a specific org, regardless of the usernames used to deploy.
BONUS POINTS: allow me to specify whether it's the ID of the target org or the source org when searching. ex -
targetorgid:00D1U000000sfXD
sourceorgid:00D1U000000sfXD1 vote -
update the wording in the change notifications - objects created sounds like Salesforce objects, not individual items
We run change monitoring and were very surprised to have 218 Objects created in Production over the weekend when no one was working. It would be good to rename this to 'items' instead to make it more clear.
1 vote -
Stamp a validated package with the username of the person who clicked 'Validate'
Currently, a validated package is created by the owner of the draft deployment package, even if someone else was the one to actually press the 'Validate' button. I would like to have the username of the person who actually pressed validation to be noted somewhere in the validated package for auditing purposes.
This would help us be compliant with processes where we need a record of separation of responsibilites bewteen users.
4 votes -
Badge
To have he possibility to have badge that could be added to the readme of a git repo. Display in green if the test classes have been successful, red if error.
The same kind of badge could be used for deployment.1 vote -
include the Name/ID of the Deployment from Salesforce into the Deployment Report generated by Gearset
Include the name/id in the deployment detail page within Salesforce in the Gearset deployment report so we can trace and match those details to a deployment run in Gearset.
4 votes -
test class not captured in deployment history
It would be nice to capture whatever test classes ran for code coverage deployment of classes/triggers in the deployment summary in the Test Results section. You already have a section for this test results so why not add the class names used in the report. We have come across many classes deployed without their appropriate test classes and it is hard tracking/documenting which test classes were used to deploy these as there are no documentations in the class.
5 votes -
Allow notification for long running jobs
Allow a for a notification to be sent when a Continuous Integration job runs longer than N minutes. Most of our jobs tend to complete in under one minute, so if a job runs longer than 30 minutes, being notified would be helpful.
1 vote
- Don't see your idea?