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
-
CI jobs view improvements
Hi Team,
when opening a CI job and then expanding them, I can see a list of PRs with status 'Succeded' for two days I thought those were the successful deployments. Technical support confirmed instead that those are the PRs where the Validation Job has succeded but not yet deployed. The view is a bit confusing because for validation jobs I would expected a status = 'Passed'.
Also, when I open the 'View History' of the actual deployment job it takes me to a view where I can see the github ID but not the PR number/name. It would be…2 votes -
Allow customization options for the Deployment Report file name
It would be nice to either have the option to set a default file name or allow the ability to set the report file name in the deployment screen.
For my organization, this would make sorting deployment reports for various projects much easier as the file name doesn't include the Package Label.
2 votes -
Expand Permission reporting on the Monitoring job
Expand Permission reporting on the Monitoring job to include Delete permissions reporting on Objects.
2 votes -
To provide the deployment history of all deployments, not only the ones from compare and deploy.
It is useful to be able to filter and download all promotion history in a similar way we can do for deployment history.
1 vote -
Allow configuring Unit Test jobs to run without code coverage
Ideally I would like to track code coverage, however due to an issue we're having with Salesforce, it's taking 12-24+ hours to run all local tests, crippling our ability to run unit tests nightly. I've discovered that when turning off code coverage when initiating test runs via the tooling API, test runs take significantly less time. We have been working with Salesforce support on this, but as a workaround it would be very useful for us to turn off code coverage for Unit Testing jobs.
1 vote -
Increase API call limits
There currently is a API limit of only 10 calls per hour for the reporting and audit API's. This makes it difficult when developing and testing applications that tie into the api. In our case we use the api to pipe the data into our observability platform for reporting and dashboarding. It would be nice to either increase to something not THAT low or to have a development override option of some sort that customers to request to temporary increase. I understand the need for some limits due to having a shared cloud platform but this seems to be on…
3 votes -
Unsubscribe from commit emails
Choose to unsubscribe / subscribe from commit emails (success and or failures) in gearset setup in order to avoid generating unwanted emails (and their PDFs) for each deployment (and save a little CO2 along the way).
1 vote -
Automatic analysis for metadata
Adopt automatic validation for API names of custom objects, custom fields, custom settings, and custom metadata types. Additionally, ensure that the "Description" field is populated to enforce documentation by administrators and developers on Salesforce metadata, including custom fields, custom objects, automation (Approval Processes, Flows, Entitlement Processes), and other applicable metadata types.
2 votes -
Help to have a change log, including the name and email of the person who changed the test level in CI jobs?
The test class level change in the job is crucial for us; if someone changes the test level to no test in place of a specific test run, components will go without a test run.
So, if we monitor things on a regular basis, we can ensure that everything is in place.
If we have a tab to get all these kinds of information, such as reports1 vote -
audit report missing PR message
The audit reports don't include much context of the deployment, which means they are pretty useless to us and do not serve our auditors' needs. Specifically, they do not include the PR message for deployments through our pipeline, which means we can't link each deployment to the specific ticket responsible for that deployment. The PR message is where we put our ticket. This information is needed for our SOX audit process. Additionally, we can not see a link back to the deployment, which would allow us to quickly reference the specific metadata files/components that were deployed.
1 vote -
Expand Notifications Capabilities
Currently 'Notifications' found under 'Settings' in 'My Account' allow for send outs for your owned connections. It would be helpful to have the ability to make notifications for connections that have been delegated to you as well.
1 vote -
Delta comparison between two unit test reports
Hi team. Would be good to have a feature that allows us the comparison between two unit test results. We are interested to export the delta errors from one day to another.
Use case: We are executing deployments for more than 50 pull requests against the same target sandbox, hence regression errors might be introduced throughout the day. We are running nightly unit test jobs and usually, in the morning, we have extra tests which are failing comparing with the previous day.
We are currently exporting the gearset errors from 2 reports, in Excel tables, and compare these ones to…
2 votes -
Terse Slack/Teams Notifications
Provide a Terse Notification format for Teams and Slack Notifications.
Currently, the amount of information in Teams and Slack notifications is satisfactory, however the presentation in the chat app is very dense and can take some time to grok when you're browsing the history of these messages either scanning the jobs that have run over the past few hours in your channel, or just trying to understand what just happened from the push notification that went to your phone.
Ideally, the first sentence is terse and is separated by white space from the remainder of the current paragraph format.
The…
1 vote -
Ability to report on runtime in Gearset Reporting API and what metadata filters were used
As part of showing the amount of time saved by using Gearset (and DevOps best practices), as well as the overall current utilization of Gearset across multiple teams and Gearset instances, being able to report on the Comparison, Validation, and Deployment runtime would be extremely beneficial. Also reporting on which metadata filter was used, if named and saved/accessible, in a comparison, validation, and deployment.
This data could also be used to identify inefficiencies in the standard metadata filters used across our Gearset instances, and potentially identify clients not deploying smaller and iteratively in order to prove with data how that…
5 votes -
Add the ability to add "Shared Mailboxes" to "Deployment Notification."
It would be logical to have the ability to add a shared mailbox to the "deployment notifications" for individuals.
The current logic is that you need to add a user, however the only way to do this is create a SF user in a DEV org for the shared mailbox which is not clean or logical for a mechanism of a notification.
1 vote -
Audit API - Production Filtering
From a compliance perspective, we only need to ingest production changes. It appears there are fields like 'SalesforceOrgType' on Anonymous Apex Endpoint and 'TargetMetadataLocationType' on Deployments Endpoint.
It would be great if we could filter those, even better if you could bring in Production Org ID / Name into that filtering ability and in response as well.
1 vote -
Ability to export deployed components for specified period of time
Instead of viewing it by deployment package, it would greatly help us to be able to export all components deployed during a specific period of time. It would help to include the following:
Deployment friendly name
Source
Target
Date and Time
Deployment Status
Owner
Metadata Type
Name
Difference Type2 votes -
Export Deployment History Additional Information
It would be great if the Deployment History was able to provide details from Source Control. Specifically, list of people who approved tickets, branch names, commit IDs, etc.
2 votes -
Include Pull Request title in the notification
Hello GS team,
Currently, the notifications from the pull request validations only include the PR number, I would like to request if it's possible to include the PR title.
Current Sample: [Gearset] CI validation job Validation job for PR #11111 failed
With the title in the subject of the notification, we can FW the results to the right teams automatically.
Thank you!
3 votes -
Gearset Service Status Page
It would be very useful to see a status page for Gearset services. Similar to other service platforms like Github (https://www.githubstatus.com/) or Salesforce trust (trust.salesforce.com)
This would be great to help determine if there are issues with deployments, or if Gearset has any sort of performance degradation.
7 votes
- Don't see your idea?