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.
334 results found
-
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.
-
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.
-
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 -
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
-
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.
-
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 -
Allow teams to share custom filters
Allow those filters we can save to be shared amongst our team!
7 votesCustom filters are now automatically shared with other members of the team and can be selected from the saved filter drop down when setting up a comparison.
Blog post on usage: https://gearset.com/blog/shared-team-comparison-filters
-
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
-
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.
-
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.
-
Allow GitHub to be a Target, not just a Source!
Let us move changes to GitHub!
5 votesWe’ve now shipped the ability to choose GitHub, Bitbucket and GitLab as the target for deployment.
Simply pick the Source Control option on the target when configuring the comparison.
-
Warn about unsaved changes to my draft deployment
The Draft Deployment feature (https://gearset.com/blog/collaborate-with-draft-deployments-from-gearset) allows me to quickly build up a deployment, but I sometimes press Next to kick off the deployment without saving the current state of things I have selected.
If the deployment fails, I sometimes can't get back and need to go to an earlier version of my draft.
It would be great if you could prompt me to save when leaving the results screen so I don't forget.
6 votesApologies – this feature got pushed back a bit! We’ve now shipped version one, with a couple of small usability tweaks coming soon.
As always, thanks for the suggestion. Let us know if it doesn’t work as expected, either here or in the in-app chat.
-
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
-
It isn't obvious that you can sort by the "selected" column
It isn't obvious that you can sort which items you have selected while inside the "Changed", "Deleted", and "All" tabs of a comparison.
It would be better if you followed common web patterns like those found in GMail with the
...symbol in the column.See attached screenshot for example
1 voteAs you identified, you can sort by selected objects by clicking the header to the right of the select all checkbox.
We’ll have a look to see if we can make this a bit easier to discover.
Thanks,
Jason. -
Use Draft deployment name as the Friendly name...
Would it be possible to have the draft deployment name, default to the friendly name under deployment history?
3 votes -
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.
-
Display deployment history in a list
Currently viewing the deployment history requires opening a pdf. If going back in time the only way to find a specific item that was deployed is to open one pdf at a time and look for the change.
It would be great if clicking on a past deploy would show items deployed in a list form on the page itself. This would make finding a past change easier.
2 votes -
Please don't try and deploy 'changed' Process builder processes.
Process Builder Flow versions appear as separate elements for deployment. Unfortunately you can't re-deploy an existing Flow, it won't let you change it, so Gearset shouldn't suggest that as an option.
2 votesThe latest release of Gearset includes additional dependency analyzers which should automatically find and resolve the issues around deploying flows. This includes detection of active flows, flow definitions, and deletions of flow definitions.
My colleague Matt has emailed you with a more detailed summary of what’s changed.
Jason.
-
HTML email template - require Letterhead
Currently when deploying an HTML email template I get an error. This is due to the Letterhead not being present at the target. If I select the letterhead in the source and deploy it along with the HTML email template the deployment succeeds.
It would be nice if Gearset could see this dependency for the Letterhead and prompt to include it as part of the deploy
1 vote
- Don't see your idea?