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.
369 results found
-
Add a `Weekly` cadence to the test runner
I need to run my own tests (ie no namespace) daily as those should never fail and if they do I need to know
For namespace tests, I just need to run them weekly, primarily to reset the "invalid" flag on apex classes that can be tripped by trivial changes. I know some will fail as we have some huge apps installed and my understanding is that it's normal for dome of those managed tests to fail.
So I would only want to run them weekly to reduce the noise from the daily failure email. Just run those on Saturday.
11 votesYou can now schedule unit test jobs to run on specific days of the week, which means you can set up a weekly cadence setting the job to run on a single day.
-
Ability to compare and migrate object data between Salesforce orgs
The metadata compare and deploy is outstanding and works well. What would save configuration and release engineers even more time would be an object data compare / sync. Sometimes, salesforce releases may only require a data migration. Hopefully, this feature will get a few upvotes from the community as well.
14 votesThis has now launched as part of our data deployment feature.
https://gearset.com/product/data-deploy
This is an opt-in feature, that doesn’t change the default security profile of Gearset for those users that choose to use metadata only
-
Filter on Columns in comparison screen
On comparison screen, would be nice if we can filter on each column on top of standard string filter
Example use case: Show me Custom object with last modified by me with modified date within this week.
Can be achieved if we can filter on "metadata type", "Changed on", "Changed by" Columns
5 votesWe’re closing this feature request as the main bulk of functionality (more advanced filtering on a per column basis) was implemented at the end of 2016.
If you have a specific interest in 1st class filtering specifically by date, could you open a new feature request for that?
Thanks,
Gearset team -
Add a 'Share Organization' shortcut under 'Actions' in Manage Organizations
For team members without access to a saved organization, the hover tip on the inactive 'Open Draft' button in Draft Deployments reads "You don't currently have permission to edit this draft. Request access from the owner of the source and target credentials".
If the org owner looks under 'Manage Organizations' to remedy this, there's no information on this page indicating how to grant access . Most users on our team are Account Members (not Account Owners), and not familiar with navigating the 'Account' menu options.
Would suggest a 'Share' shortcut under Actions in 'Manage Organizations' to take the org owner…
1 vote -
Exporting Scheduled Test Results to File
We would like to see the ability to export the scheduled test results to PDF or Spreadsheet. This will allow us to associate test results with our internal work items and allow visibility into the test results. I understand that users can view the test results with no license. However, i see value in having the export available; similar to the export of the deployment report.
1 voteYou can now export test results as an Excel file from the test run history by clicking the Excel icon.
-
Have CI jobs work using BitBucket webhooks
Just like it is already with GitHub.
1 voteSupport for Bitbucket webhooks for CI jobs is now live if you want to test it out.
Stephen
-
Combine multiple deploy packages into one
It would be nice to have the ability to select multiple packages in the deployment history, and clone all of them into one comprehensive deployment. This would help when there are multiple features moved at different times to a QA environment, but would like to move them all at once to Production.
28 votes -
Text results on Monitoring to multiple phone numbers
Allow text message notifications to multiple phone numbers
3 votesYou can now add multiple phone numbers to receive text notifications for Monitoring and CI jobs.
-
CI Jobs - Partial Deployments
Allow partial deployments when changes are committed into a branch, so instead of trying to re-deploy the full repo, we should have an option to allow deployment for only the changed items.
6 votesCI jobs can now be set to deploy only certain types of metadata change: new, changed, deleted. If only “changed” is selected, no new metadata or deletions will be pushed by the job, only modifications to metadata that exists in both source and target. This selection is found in the job creation/edit screen. You can also specify whether you want the CI job to respect a package.xml file when deploying from a repository for even finer control over what metadata it deploys.
-
Ability to select Field Sets as a separate item
It seems that Field Sets are deployed by deploying the object that they are related to.
This doesn't work well for me because I have admins changing objects in production, but I often need to deploy a Field Set to go with my code.
Currently, I'm jumping out of Gearset and deploying a Change Set with just the Field Sets, then coming back to Gearset to deploy my code.
It would be nice if I could select just the Field Sets and deploy them without changing anything else related to the object.
8 votesField sets are currently deployable as individual items assuming the object they belong to already exists in some form in the target. If the object the field sets belong to doesn’t exist in target yet, then it must first be partially created in the target for Gearset to be able to deploy individual sub components. Thanks for the suggestion!
-
Ability to create CI jobs from GitHub Enterprise
I expect parity between GitHub and GitHub Enterprise when it comes to creating CI jobs and CI jobs with web hooks.
1 vote -
Add support to run tests that are in a namespace
Add the ability to run tests that are behind a specified namespace. This would allow developers to run their own tests in a test org with other packages installed.
1 voteThis is now implemented – when setting up a test monitor you can now include a comma separated list of namespaces to run tests in.
-
Changed By / Change On reporting incorrect user
Changed By / Change On reporting incorrect user when comparing to Salesforce orgs (sandbox to prod)
2 votesI’m going to close this post. Unfortunately Salesforce provides the information and we’re simply reporting it so it’s beyond our control. I’ve provided 3 scenarios in the post about what can happen. I’m sure we’ll uncover more over time!
-
Edit CI Filters on an Existing Job
Be able to adjust the filters for a CI Job that is already running. Currently you would have to delete the job, adjust the filter, and then setup the job again.
2 votesWe’ve now added the ability to edit CI filters on an existing job.
We’ve also added:
- see currently running CI jobs
- Manually kick off an existing job instead of waiting for the schedule to start -
A "Run Now" for CI Jobs
Have a button on the CI page that will allow you to run the CI job immediately instead of waiting four hours to see if the job was successful.
2 votesHi,
we’ve now added the ‘Run now’ functionality for CI jobs. Simply select the Run button from the actions column.
-
Allow filtering in deployments tab
On the deployment screens I'd like to have options to filter the list.
Some suggestions:
Team Member
Date Range
Target Username2 votesSorting and filtering have now been added to the validation history page – that change is going through the release pipeline and should be released in the next 24 hours.
I’m going to close this ticket since the main points have been addressed. If filtering by date range is an important feature to you, I’d appreciate it if you could create a separate improvement suggestion for it so that we can prioritise it appropriately :)
Thanks,
Oli
-
Monitor Orgs feature -- Turn off monitoring for metadata types
Monitoring orgs is great, except for orgs (in my case) that have Site.com Metadata. Each day that the monitoring runs it reports changes because of the MD5 checksum value is changed.
So to see the changes from the monitoring screen I have to click into the org and the monitored job, click into history, then into comparison. When nothing on the org has really changed other than the checksum value it shows differences (which makes sense).
What I would like is the ability to turn of monitoring for this metadata type. Or possibly more than just this type if there…
1 voteWe have removed the Site.com metadata type from the default comparison set, so change monitoring jobs will no longer include this by default.
In addition, when you create your monitoring job, you can specify which metadata filter you’d like to use. This will let you choose exactly which types of metadata to monitor for changes.
-
Source Code Metrics
Hello,
I think it would be very nice to connect the repository either to Code Climate for apex or to Source Code Scanner for apex and Security.
Also it would be nice to connect it to Heroku Lightning CLI for aura bundles (application and components).
2 votesGearset now has static code analysis as part of the Monitoring and Backup tab, with plans to add it to other workflows in the app
-
Custom login URLs
We deal with SF instances that do not login with the standard login.salesforce.com or test.salesforce.com.
It would be nice to see an option for custom domain or custom url that can be used for either OAuth or username/password authentication.
2 votesThanks for the feedback!
This was shipped today – on the comparison screen you can now add an org with a custom domain by selecting “My Domain (Government Cloud)” from the Salesforce authentication type dropdown. This works with Government Cloud orgs, and also any Salesforce org that has a custom My Domain url.
We don’t currently support My Domain orgs with username/password authentication. Please let us know if that’s a problem for you, or if the feature doesn’t work as expected.
-
Object level filters for Monitoring
Object level filters for Monitoring
1 vote
- Don't see your idea?