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.
1444 results found
-
Remove files from a PR
I want the ability in Gearset to selectively remove files from a branch or PR without running another comparison.
I have an admin that frequently "over commits" too many things.
Often its bad enough that its just easiest for them to delete the branch in github then start over in gearset.
The problem then is that starting over from scratch, a day or two since they worked on it, and they will make a different mistake.
I'm aware of a few features, like
Delete the branch in Github and start over in gearset
- Seems to be the easiest to me
…
18 votes -
4 votes
-
Compare Types on Comparison
For the pipelines observed when creating a feature branch and during comparison runs, a default filter is applied to the compared types without any metadata types selected (0). We would like to have a custom filter with metadata types for a specific pipeline pre-selected by default when the feature branch initiates the comparison.
3 votes -
Ability to export results of historic test run
When successfully validating a pull request, there is a "view details" link under the "Merge and validation checks" section. When clicked, in the new page that opens there is a button "Export test results…" that allows me to download the test results in excel file with detailed precision, reporting each test method duration.
Unfortunately this feature is only accessible when PR are being validated, and disappears when checking historic PRs already closed and deployed. Would it be possible to provide such data?
1 vote -
Allow customization options for the Deployment Report file name
It would be nice to either have the option to set a default file name or allow the ability to set the report file name in the deployment screen.
For my organization, this would make sorting deployment reports for various projects much easier as the file name doesn't include the Package Label.
2 votes -
Expand Permission reporting on the Monitoring job
Expand Permission reporting on the Monitoring job to include Delete permissions reporting on Objects.
2 votes -
Version Control Commit History in Comparisons
When you compare a version control repo to an environment, it would be awesome to see the commit history get pulled in so you can quickly filter for a specific commit message(s)
0 votes -
Save sort order in Saved comparison pairs
It would be nice that the chosen sort order of the saved comparison pairs could be saved.
If I choose to sort the saved comparison pairs on Friendly name and i open a new tab of gearset, the saved comparison pairs in the new tab are sorted on last used. It would be nice that in the new tab, the saved comparison pairs are sorted based on the same column as the previous tab.3 votes -
Add an option to ignore API version differences during comparisons
When comparing Apex, and other files with API versions the difference engine will mark any files with higher API version as "changed", even if the API version is the only change. This can be undesirable when there have been bulk updates to the API version that have not been made in the development environments. It would be great if the comparison engine could make it clearer when the only difference between two files is an API version (especially when the target is on a higher API version)
2 votes -
To provide the deployment history of all deployments, not only the ones from compare and deploy.
It is useful to be able to filter and download all promotion history in a similar way we can do for deployment history.
1 vote -
Write deployment results to a custom Object.
We use a custom ticket object in our processes to track salesforce change requests. The ability to write deployment, validation results to a custom object would be very helpful.
1 vote -
Multiple screens
I work with 2-3 screens. It would be great to be able to split the comparison settings to one screen and have the xml, flow navigator, lightning page visualizer,... on another screen. That way users can see more as they work. As a photographer I use Adobe photoshop and lightroom both applications allow splitting the controls and output.
1 vote -
The Ability to add deployments to a folder or tagging them...
On the Validated packages, Draft Deployments, Depolyment history it would be great if users could create folders or tags to group deployment or validated packages. Use case: Team has a large deployment that will be split into multiple parts a folder or tagging would help with organization and tracking.
1 vote -
The destructiveChangesPost.xml file should be processed in manual comparison
The destructiveChangesPost.xml should be processed when using local file as a source for manual comparison. Ideally the items listed in the destructive file should be used as filter for which to show in the Deleted filter
1 vote -
Ability it use SOQL to provide complex filters on Vlocity and Salesforce Metadata types to create custom Compare & Deploy Filters
I would like to have the ability to enter SOQL queries to filter Metadata types and data. Currently you can only use Object or Regex when you try to filter the data to fine tune the comparison. We are looking to do this for Vlocity and Salesforce metadata types and objects
2 votes -
Make the commit hash clickable in Pipeline PR Commits tab
This is rather trivial, but also seemingly a quick-win.
In the Commits tab on the Pull Request details screen in the Pipeline, make the 7-character commit hash a hyperlink that opens a new tab into github.
It is minor, would save me 1's of seconds, but it seems like an easy win - the commit url is just {{git-origin-url}}/commit/{{7-char-hash}}
2 votes -
Allow Dev Updates to be Qued
Allow dev updates to be in a que so that you dont run into the problem of updating to many at the same time.
1 vote -
Update all Dev's button
Create a Update All Dev Sandbox button in a pipeline that allows you to quickly update all of the devs at once instead of clicking into each one.
1 vote -
Notify when PR is automatically created (e.g. back propagation)
Notify the developer when a Pull Request is automatically created. For example when next pipeline stage is reached and a PR is automatically created or when a back propagation PR is automatically created.
A comment in related Jira ticket would be very helpful.4 votes -
Allow for different pull request messages.
I would like the ability to have different pull requests message per pull request that is autogenerated when you move through the pipeline.
Example: When I first create a pull request from dev to my next static environment the message would only pertain to that static environment. So from Dev to UAT I would include a pull request message pertaining to testing.
Then after that I would move from UAT to Staging so the message would be something about the testing and how it is complete and ready to move to staging which is our integration environment.
Then when that…
1 vote
- Don't see your idea?