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.
337 results found
-
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 -
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 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.
-
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 -
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. -
Allow me to exclude metadata.
I have certain metadata which is broken or dangerous to migrate from a dev org, I'd like to exclude it from this and subsequent releases. If I could 'right click' and ignore it that would be good.
20 votes -
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 -
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 -
Deploy detected changes to other orgs
Being able to detect and roll back changes to orgs through the change monitoring is cool, but what I'd really like is to deploy detected changes to other orgs.
For example, if we detect a new configuration change to Production, being able to clone that change back down into our Sandboxes directly from the monitoring snapshot would be a real time saver. Or if someone deleted something in Production, being able to make that destructive change down into the Sandbox.
It would help us remove the step of running the comparison and pushing the changes after seeing a monitoring job…
14 votesThis is now shipped and live in the app! We’ve written a small blog post that walks through the feature and the use case.
https://gearset.com/blog/migrating-quick-fixes-in-salesforce-to-source-control
-
"Run now" button for test automation
Adding the ability to kick off a test job on demand, rather than the daily or configurable frequency
9 votes -
Deploy from change monitoring result
It would be great to be able to deploy changes detected in a specific change monitor result from the report history. Either to roll them back if they are unwanted, or deploy them to other orgs to replicate them into dev boxes.
0 votesWe think there are two parts to this request.
We’ve now added the ability to roll back changes from a change monitor result – you can selectively remove any changes made to that org on a daily basis by comparing from a snapshot to live state.
We’re now working on adding support to clone a detected change and deploy it to other orgs. This would let you push changes made in Prod down to a Sandbox, for example.
The second part of this is contained in another ticket, so we’re marking this one as completed.
-
Deploy to source control
It would be great to be able to deploy changes to my source control system, as well as from them, from the hosted app.
0 votes -
Track deployment validation errors more easily
When a deployment or validation fails, Gearset helpfully provides a list of the failure reasons. But when I go back to the comparison to make the changes, it's easy to lose track of what needs to be fixed. Adding the ability to export or save the warnings so I can easily work through then as a reference list.
0 votesYou can now export deployment failures as a CSV file from the validation or deployment failure screens. The CSV show the objects and their associated errors.
We may add additional functionality to this over the coming months to expand on how we track and display errors to make the process even easier.
- Don't see your idea?