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.
1280 results found
-
Provide a way to get the debug logs of failing tests
Sometimes my tests are failing when they run during the automated run at night, but, when I log in and run the tests manually, they pass. I can see the failure stack trace, but I was wondering if there is any way to keep/view the debug logs from the failed tests so I can try to understand why they fail at night, but work during the day?
6 votes -
Include both dates on comparison export
The sheet exported from a comparison currently includes only one date column. It is unclear which org this refers to. It would be great if it included two columns (one per org) so that one didn't have to individually look up the item to determine which version is newer.
5 votes -
Modify the email address for manual deployment notifications
Being able to modify the default email address for deployment notifications, as for automated jobs, would help keep the others in my team notified of any manual deployments we run.
4 votes -
Ability to pause subscriptions for inactive users
Manage users on "My Team", so we can activate/deactivate users and then save on licences that are not used until reassigned.
6 votes -
User Account Specific Validation Errors
When deploying objects such as reports to a Target ORG, sometimes the reports are shared with a user in the source ORG. If the user does not exist in the Target ORG, the validation throws an error. Would it be feasible to add objects, such as reports, to the Warnings / Fixes screen so we can easily select how to handle user specific dependencies? Maybe we can chose to enter a new username or simply remove the shared with permission on the object?
2 votes -
Differentiate XML and Code differences in the comparison
I would find it very useful if the comparison result highlighted if the difference was in the XML or the Code (or both) for each item. This would especially save time when there are a lot of differences.
7 votesThanks for the suggestion Celio.
We think this should be possible to do and are doing some background work into how to manage and display this. More details to come soon.
Thanks,
Jason. -
Unselect all standard profiles & related permission
Often you want to deploy Admin profile and (x) custom profiles. Compare and deploy picks up hundreds of entries for standard profiles which are surplus to requirements. A single click way would be veryuseful.
4 votes -
Specify tests to run on the test monitoring jobs
Some of my orgs have many tests, and I don't always want to run all of them on a daily basis. Being able to specify which tests are run daily would be great.
7 votes -
Manage Orgs Re-authorization returns you to a default sorted list.
I refreshed a sandbox. I need to re-auth my orgs. I go to Manage Orgs, and sort by my friendly name. I click re-auth, and OAuth is successful and the app tells me I did a good job. But the page it returns me to is using a different sort then I left the page with. ie, it sorts the list by username again. Just extra button clicking I'd like to get rid of if possible. I have to re-auth orgs all the time.
2 votes -
"Changed on" date on source control side of comparison does not show
We have no way of knowing when the files were last changed on the source control side. Tried only with BitBucket though.
10 votesThat is something we should definitely show. We’ve added it to our investigation list to see if it can be added into the app.
Thanks,
Jason. -
Provide option to disable parallel apex testing in Scheduled Tests
Scheduled Test runs can fail due to UNABLETOLOCK_ROW errors. This is due to what amounts to a bug in SF: accessing public custom settings in tests which are run in parallel can cause deadlocks. Really, the tests ought to be isolated from each other, but they are not. See:
The workaround in SF is to disable parallel apex testing.
If Gearset could do that during the scheduled test run, it would prevent false test failures.
I guess I could change the option on the SF org, but sometimes parallel testing is useful, so I wouldn't want to…
9 votes -
Send a link to the report in the notification
It'd be nice to have a link to the report included in the notification for any scheduled monitoring, test run or deployment/validation.
8 votesThanks for the suggestion.
When you run a deployment, the deployment success email contains the PDF of the deployment report, as well as a link to your deployment history to view the full information.
For the test/change monitoring emails, what sort of report would you like to see? Would you like to see the full information on tests run or just a summary of key stats?
We don’t currently provide the ability to export PDF reports for our change and test monitoring jobs in the same way as our deployments, but it’s something we’ve been thinking about putting in.
Thanks,
Jason. -
Add ability to exclude specific files/folders of repo from a compare with source control
Currently, if you try to compare a repository to a Salesforce org, it will throw an error with only the ability to send a report to Gearset if the repository contains files that are not compatible (gulp files, package.json, etc. at the root of the repo or any folder that isn't corresponding to a Salesforce type of file).
My suggestion would be to add the ability for the user to exclude those files or folders from the compare and retry when it fails. This issue currently prevents us to use source control in the comparisons.
7 votes -
Scroll to top of category, when switch between All Items, Changed Items etc
Just a user preference item – when you switch tabs (ex: New Objects to Deleted Objects), it doesn’t place you at the top of the window.
So if I scroll down through all the New Objects and then switch tabs to the Deleted Objects, it just places me in the same relative location as I was in the New Objects tab.
It would be nice to have it reset to the top of each window when I switch tabs.
2 votes -
Specified Test Level Suggestion
Hello,
It would be very nice to be able to have a test classes suggestion when doing a deployment with "specified test level". The suggestion will ensure the package elements will be covered at least by 75% and so speed up the deployment.
1 vote -
When migrating ReportFolders, either remove running user or let me map users between Sandboxes/environments
When migrating ReportFolders, either remove running user or let me map users between Sandboxes/environments
The SharedTo User doesn't exist in the target org causing my deployment to fail.
2 votes -
Add merge functionality to the diff tool
Extend the diff tool to allow the user to perform a merge, creating a new version of the component that contains some changes from the source version and some changes from the target version. This would be very useful in a team development scenario where multiple devs are working on features in individual dev sandboxes and then pushing completed features into an integration sandbox.
82 votesMerging differences between Apex classes and VisualForce pages is difficult to do automatically due to the understanding required by the developer. For differences between two orgs in other object types, Gearset helps you sidestep that with our granular comparison results. This blog post explains more: https://gearset.com/blog/merging-salesforce-metadata
-
Changing executing time in a Job does not automaticalely start the Jobs!!
No information is given!!
1 vote -
Show the Label as a column in the comparison screen
At present the comparison screen, Name column, only shows the information from the API name, but not the Label (as seen in Setup > Object Manager > Label column).
When the Label is wildly different from the API name, is would be super useful to have the Label displayed as a column, instead of having to find it in the XML viewer.
1 vote -
When running "Compare and Deploy", or via a similar mechanism, allow the target to be a local zip
In rarer situations where I need to make some manual adjustments to the metadata XML for a deployment, I'd like to be able to download the metadata to adjust it. Today you need to go through a compare, and at the end, you can download the package, but this can be problematic, since you have to choose the target org, there need to be differences, etc.
Instead, it would be useful to just choose the source org, select the metadata items, and save the package, without a target org needed.
1 vote
- Don't see your idea?