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.
1308 results found
-
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 -
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
…
15 votes -
Split Lightning Page Metadata Type
Think the Lightning Page metadata type needs to be split into 2 categories. Reason being it is the one metadata type that causes comparisons to run for extremely long times or even crash/time out. This happens because it trying to compare all of the lightning email templates users make. It would be better if lightning email templates were their own metadata type and the lightning page type was actually just lightning pages created for objects.
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 -
Cancel Comparison
I would like to be able to cancel comparison jobs so that I can totally reset the metadata selections and run it at a different time instead of making the modifications during its run time and possibly taking longer because of the changes.
1 vote -
Auto navigate to next conflict after resolve
After I have resolved a file/metadata component I would like it to auto navigate to the next item in the list.
1 vote -
Custom Sort Conflict files by metadata type
I would like to be able to sort conflicting files by metadata type in the conflict screen. That way I can resolve conflicts in a more organized fashion.
1 vote -
Update Slack notification messages format
Update the slack messages to more clearly define what happened in the action.
There should be a more clear title to the slack message. It should define what item was doing what. Currently that is grouped into a description which does not show on slack notifications.
CI job notifications should have a more clear "from where to where" section in the notification. Currently its grouped into the description.
1 vote -
All available branches display
Create a view that displays all active and available branches and there current commits and pull requests. That way if there a multiple branches per environment a release manager can see everything that is going on instead of having to click into each environment in the pipeline or going into git.
1 vote -
Show Auto resolved conflicts
When in the conflict resolution screen it would be nice to quickly see all files that have been auto resolved. Maybe with a icon of some sort on the left hand side next to the circle icon for resolved or not resolved.
1 vote
- Don't see your idea?