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.
1309 results found
-
Allow Adjusted Column Sizes to Persist in the Comparison Table
Have adjusted column sizes persist once they've been adjusted in the comparison table instead of resetting with each selection. Deploying changes to permission sets could be dramatically streamlined if it's possible to maintain resized columns. If column sizes were set to accommodate the name instead of giving them all the same size, that would also be a huge improvement. The other columns don't include as much info as the name column so it's a waste to give them so much space. It is also inconvenient to caret down in permission sets especially when looking for multiple fields in one permission…
2 votes -
Add a Button to Retry Validation on Updates
The new Updates feature is great, but there isn't a "retry" button when there are validation errors to resolve. It's not very intuitive to have to cancel the update and go start over to retry after fixing validation errors. Currently it just shows that the validation failed and the update can be cancelled. It isn't clear what to do after resolving the validation error, and a retry validation button would simplify the process.
I had an error related to a manual change that needed to be enabled in my sandbox, and I had to cancel the update to get it…2 votes -
Allow configuration of where pull request/merge updates are posted in Jira. User comments are being missed because of the volume of updates.
Allow configuration of where pull request/merge updates are posted in Jira. User comments are being missed because of the volume of updates from Gearset when moving a set of changes through the pipeline. These updates are important and we want to keep them, however having the ability of moving them to another tab/section on the Jira ticket would mean we could keep the comments section for user comments only.
2 votes -
documentation
I have been really impressed by the visualizations on the Compare and Deploy interface. Particularly the lightning page layouts and flows. One of my most time consuming tasks is creating internal documentation and I have not found a tool that allows me to capture the level of detail that I want in an efficient way. It would be great if I could export the visualizations at the bottom of the compare and deploy screen. It would be even better if it could export directly to Confluence.
2 votes -
Job Completion Percentage
I would like to see more details about the status of a deployment or validation job in the Pipeline. Right now it just says job is running. I would like to see a estimated percentage of component validated/deployed against the total. Also maybe a running time estimate.
2 votes -
Allow configuring Unit Test jobs to run without code coverage
Ideally I would like to track code coverage, however due to an issue we're having with Salesforce, it's taking 12-24+ hours to run all local tests, crippling our ability to run unit tests nightly. I've discovered that when turning off code coverage when initiating test runs via the tooling API, test runs take significantly less time. We have been working with Salesforce support on this, but as a workaround it would be very useful for us to turn off code coverage for Unit Testing jobs.
2 votes -
CI jobs view improvements
Hi Team,
when opening a CI job and then expanding them, I can see a list of PRs with status 'Succeded' for two days I thought those were the successful deployments. Technical support confirmed instead that those are the PRs where the Validation Job has succeded but not yet deployed. The view is a bit confusing because for validation jobs I would expected a status = 'Passed'.
Also, when I open the 'View History' of the actual deployment job it takes me to a view where I can see the github ID but not the PR number/name. It would be…2 votes -
Offer Japan data residency
We are headquartered in Japan. Japan has data residency requirements for data backups/deployments and even metadata deployments/processing.
Please add the option for a Japan hosted Gearset account.
2 votes -
Allow out of order Update deployment
Currently you can only deselect and select update elements in an order. For example I have 3 recent updates ordered 1 to 3. One being the oldest and first update and 3 being the newest and last update. The current functionality would require me to select item 1 if I wanted to also update item 2. And if I wanted to update item 3 I would have to select all the items before it.
I would like to select each one individual no matter there deployment history. Often I need to do this because the updates have no relation to…
2 votes -
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 -
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 -
Update assignee for jira tickets
According to our team flow once feature is deployed to UAT environment, linked task in Jira must be reassigned to QA team lead to start testing.
Right now this is completely manual process.
It would be nice if we can specify assignee in gearset pipeline settings.2 votes -
Add the "cloned from" friendly name somewhere on the comparison page.
This suggestion is specific to comparisons that are initiated by cloning a package (that already has been named). Gearset / salesforce takes a bit of time to finish its comparison/validation, so often times I'll open up to 5+ tabs one for each of my gearset deployments. As the comparisons complete, I'll move between the tabs to progress through the steps, but as you can imagine it gets confusing which compare is cloned from which deployment.
Possible ways to display on UI:
When cloning a single package -
e.g.
Apps-87431When multiple packages are combined -
e.g.
Apps-87431
Apps-87431-Step2
Apps-87431-AddFieldUsually,…
2 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 -
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 -
Display auto-merged files during Conflict Resolution
The Conflict Resolution only displays files that require manual resolution. Sometimes I want to see the files that were automatically merged without human intervention.
The only way to see this is to submit a resolution as is, then read through the file changes again to look for files that were auto merged/resolved from target instead of source.
2 votes -
Allow users to select a default comparison view between 'Permissions View' and 'XML view'.
During comparisons, I constantly have to select the XML view when I click through rows of metadata as it keeps defaulting back to the Permissions View, I don't particularly find the permissions view that useful and I'm also used to XML views, would appreciate if you could give users a choice in a 'default' view to improve experience.
2 votes -
Automatic analysis for metadata
Adopt automatic validation for API names of custom objects, custom fields, custom settings, and custom metadata types. Additionally, ensure that the "Description" field is populated to enforce documentation by administrators and developers on Salesforce metadata, including custom fields, custom objects, automation (Approval Processes, Flows, Entitlement Processes), and other applicable metadata types.
2 votes -
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
- Don't see your idea?