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.
92 results found
-
Consolidated Reporting for CI Jobs
Hello. One item we struggle with is keeping track of CI Deployments that didn't fail, but didn't deploy as expected. The two causes we usually see are:
1) Something was removed by problem analyzer
2) We deployed something that Salesforce says succeeded, but no changes were made (e.g. deletion of picklist choices)We currently have about 100 CI jobs which makes it impractical to go into each one.
The proposed format would look like a csv export:
Job Name, Date, # Created, # Updated, # Deleted, # fixed by problem analyzer
Opening a CI job history looks fine, but we'd…
1 vote -
Have an ability to modify message which is posted to Slack channel.
It would be nice to have the ability to modify this notification message somehow.
E.g. include a number of PR which was merged into the main branch. Or remove extra information such number of deployed components.now it looks too big
Gearset Continuous Integration
A continuous integration run succeeded for ***** CI/CD. The job was a deployment.
Changed objects
3
New objects
0
Deleted objects
0
Source commit
1c***f2b3 votes -
Add Time Column to the CI Deployment page
Due to recent latency issues regarding SF performance issues, I would like to quickly see how long each CI job takes without having to download an individual report for each job. This can either be solved by either:
Adding a field to the CI Deployment page so that I can compare each CI job
Allow me to extract a complete report of all of the CI jobs and open it in excel with the time column so that I can compare the values. I can currently do this from the Deployment history page, however this does not include the CI…
2 votes -
change monitoring for scratch orgs
The Change Monitoring feature only supports normal orgs (sandbox, developer, prod). It does not support scratch orgs
For use cases where developers inadvertently let their scratch org expire with pending, uncommitted work, it would be nice to recover the work before and after the scratch org expires
2 votes -
Ability to audit what users have done in Gearset
Hi, I suggest there should be a feature which monitors what the users within your orgs have done in Gearset. As we can currently are able to view both comparison and deployment history, however this does not give an audit trail of who has changed what and where.
For Example, the ability to review changes that a user has made to gearset comparison filters.5 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 -
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 -
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 -
Extend the functionality of configuring when are monitoring jobs run
Hey,
Currently it is possible to configure at what time during the day you we want to run the configuration jobs.For the org monitoring jobs, we really love that this is done daily, but for unit tests, we would love if we could configure the jobs to run the job weekly or monthly and not every day.
1 vote -
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.
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.
1 vote -
Include code coverage in deployment report
Hi,
I want to use the deployment report to monitor your progress towards improving the quality of our code.
So I need code coverage to be included in this report.6 votes -
Allow team member to create unit test job based on the shared connection
I try to create the unit test job but the org connection is available to me even it is shared to me with the deployment permission. I have to either create a new connection or let my colleague who is the owner of the connection do it now,
Thank you!
1 vote -
Send email alert when monitoring job fails
It would be helpful if Gearset would notify the user when connection problems cause a monitoring job to fail.
For example, if the error "Error while getting access token due to expired access" occurs, Gearset could send an email to the author of the monitoring job informing them of the problem.
2 votes -
Add the ability to create some custom reporting against metadata change monitoring
I would like the ability to report on changes for an org over a time period grouped by metadata type or user. Filters would be by data, user, metadata type, change type. Would like to export or email the report too.
1 vote -
Add a filter in monitoring job to exclude changes done by Gearset
To help identify changes done manually to the org it would be nice to have a filter which excludes all the changes done by Gearset deployment.
2 votes -
Friendly name should be surfaced on the deployment summary page.
The Friendly Name should be surfaced on the deployment summary page, either as a row in the "Summary" section or in its own section, similar to Deployment Notes.
We often track deployments by saving links to the deployment summary. But there is not an easy way to grab the friendly name if we want to search the deployment report; for example to combine packages.
4 votes -
Add Salesforce ID to Export History button
Can you add the Salesforce ID to the Export History button for reconciliation purpose.
We currently have to manually match the Salesforce ID in Gearset with the Salesforce ID on the Salesforce Deployment Status page to get the reference between the source ticket in Jira and the deployed change for compliance purpose which is a time consuming process.2 votes -
To give the option to export , Class wise test coverage report in some Excel format
To give the option to export , Class wise test coverage report in some Excel format
3 votes -
Add additional controls to Monitor
Hello Gearset,
We are exploring using the "Monitoring" functionality to audit our Salesforce production metadata changes for our IT Controls. It looked promising until we found out that anyone on the team can edit any monitor job setting, which creates a loophole in the controls that we can't monitor the monitor.
So I'm curious to learn from Gearset whether any of the following can be done/requested:
* Can we limit the Monitor jobs to only be editable by the person who created it?
* Can we show either an audit history or LastModifedBy/LastModifiedTime of the Monitor job?
* If the…4 votes
- Don't see your idea?