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.
293 results found
-
Show history of changes for a component
When performing forensic analysis regarding how or why something started working differently, it would be a great timesaver to be able to select a component and then be able to select the data comparisons for just that component. For example, select an apex class and then pick date dates so the system can display what changed. I would expect that this would be quicker than going into Monitoring Histories and picking each date and waiting for it to build the entire comparison of everything that changed and then having to find the component of interest.
A follow on to this…
1 vote -
Remind repo owner to upgrade metadata on SFDC version change
Your blog post https://gearset.com/blog/mdapi-versioning-and-version-control says it all under the paragraph labeled "Upgradingyour repository's metadata"
But there's no real reminder to tell the team that this is a meritorious idea. My suggestion is that for the first 30 days after PROD is updated, you could display (in color) some alert (or maybe introduce a messages feature) wherein you tell the team that the repo's package.xml is out of date (version wise) with PROD version and provide pointers on how to upgrade, including nuances like Flows (v44).
It is too easy to get lazy and leave the repo metadata out of date…
1 vote -
Enable Defaults or Recently Used on Clone Deployment Page
When you clone a deployment package you have to select your Source details, but the selections do not default to the the last used settings or to a recently/commonly used settings. This is a minor annoyance but in other parts of GS you have the last selected options already selected based on user history, so hoping you can extend this to the Clone page
1 vote -
Export snapshot of production org to git
I'd like to be able to export a snapshot of all the metadata from my production org (include all components) to my git repository by clicking a single button.
After every release, it's worth taking whole metadata export from the org to git for the next/on-going releases.
For now, we have to create a couple of metadata projects to export the metadata to git, which is a tedious job and takes a lot of time.
1 vote -
Target Process Integration
Agile/sprint planning tool similar to JIRA
1 vote -
Ability to set a friendly name to the package
Should it be possible to set an equivalent of "friendly name" in Gearset but one that can also be spread to Saleforfce.
1 vote -
Add system log fields for created and updated operations for filters
It will be helpful if we know who/when a filter is changed. And it would be great if we could lock the filters as an owner.
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 -
Pending Validation - Copy from Pending Deployment
Similar to "Pending Deployments" It would be nice to see pending validations. We have several users in gearset, so if we are trying to validate something while someone has already initiated a validation, we receive the error that set up has been locked. So prior to validating a package, it would be great to check if anyone is in the process.
1 vote -
Test run details: show failed tests tab first
When user clicks on test run details, Gearset defaults to the successes tab. But no one clicks on test Run details to see successes; they want to see failures. Default tab should be failures, especially if non-zero
Saves user a click and supports DWIM - "do what I mean" when clicking Test Run Details
1 vote -
More Details for Open Draft Deployments: Show Name & Refresh Date
When you open a Draft Deployment it would be great to see its name on the deployment page as well as its refresh date. I understand that when you open a draft deployment you're seeing a snapshot from when it was created or refreshed.
1 vote -
Have access to multiple pull request templates
Currently we can only access one pull request template named pullrequesttemplate from Gearset.
I would like to be able to access a list of templates.
This would allow us to have precise template for each team using Gearset.0 votes -
Email Notification whenever deployment is successful
it would be good if we can send email notification to Users whenever we successfully deploy components to specific Org regardless of CI job.
0 votes
- Don't see your idea?