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.
369 results found
-
Change default sort order of Saved Comparison Pairs to use 'Friendly Name' (or last used sort column)
The new Saved Comparison Pairs feature is great! However, the page appears to load connections in a seemingly 'random' order on each use.
Confirmed with Gearset Support the default sort order is by create date of each connection pair. However, if feature is used with multiple connection pairs spanning multiple individual instances this requires manual re-sorting of connections every time page is loaded if you want to view pairs logically by naming convention (e.g. Alpha 1->2, Alpha 2->3, Bravo 1-> 2 , Bravo 2 -> 3 etc.) or something other than system create date.
2 votesSorting by “Last used” column has now been fixed.
-
Include more details in webhook notifications
It would be great if webhook would include, at least, the same information as email notifications. For example, Unit Testing job notifications via email contains the details about the unit tests that failed; however, webhook notification don't. We wanted to use webhooks to get notifications in MS Teams but without the same details, it's not that useful.
2 votes -
Allow Team Members to Run Scheduled Unit Test Jobs
Execute Others’ Unit Tests
John Doe creates daily unit test job for SuperHeros R Us. He schedules it to run nightly.
Jane Smith, a member of the same Gearset team, is responsible for doing the weekly deploy for SuperHeros R Us. The unit test job from the previous day has failed (it had been previously working). Jane makes updates to the tests, and needs to re-run the unit test job. But she does not have permissions and John is out on PTO for the day. So… she needs to do it manually.14 votesReleased on December 31st, 2020
Test monitors can now be run by anyone who has validation access to the org being tested. -
Add a way to "Save" or "Save As" updated filters when in the Refresh Comparison window (like you can in the Compare and Deploy window)
When in the Refresh Comparison window, it seems there's no way to "Save" or "Save As" the updated filters. Looks like you can only access that feature via Manage Custom Filters from the Compare and Deploy screen
Any chance we could get that added? It would be super useful!
5 votesReleased on February 22nd, 2021
-
4 votes
When creating an account, a user can now choose to create a Gearset team that has data and metadata stored in the Australia.
-
Retain source control branch selection when cancelling a comparison
If you click "compare now" and then click "cancel" before it finishes, the "compare metadata" screen retains your selection for orgs, but does not retain the branch selection for source control.
It defaults to the first branch by alphabetical order versus what I selected before I cancelled. This can cause confusion for users who do not notice.
1 voteThis has now been implemented and should have the expected behaviour
-
Rerun Github validation on a PR without a new commit
When a CI job is set to run on a PR creation, if the source destination is missing something that the deploy requires, it will fail. To solve this, we must go to the source destination, make settings changes, and then make an empty commit to the pull request to re-run the CI.
It would be nice for there to be a link or button in Gearset to rerun the CI and update the Pull Request that the validation was successful.
2 votesIn the ‘continuous integration dashboard’ in Gearset, for ‘validate pull request’ jobs, there is a ‘run now’ play button to run the job manually. You can therefore update the target and then re-run the PR validation without needing an additional commit.
To be able to run the ‘validate pull request’ job manually, you need to have permission to run the parent CI job manually (e.g. be the job owner).
-
Associate pull requests to work items in Azure DevOps
When you create a pull request from gearset, the pull request isn't associated with the Azure DevOps work item.
9 votesWe've enhanced Azure DevOps (ADO) integration! You can now associate work items with pull requests directly through the ADO sidebar.
This improvement leverages ADO's native features for a more seamless and efficient workflow.
-
Add a search function to the Monitoring > Unit Tests
Add a search function to the Monitoring > Unit Test page to quickly find a specific Test outcome
1 voteReleased on 07/01/2021
-
Exclude LWC Jest files from validation and deployment
We introduced LWC - Jest tests for our project, which seems to cause validation errors with Gearset.
As per Salesforce recommendations it is recommended to keep jest tests only locally and in VCS and avoid trying to push them to SF as they would cause validation errors.
Is there an forward path that allows us to tell Gearset to exclude LWC - Jest files from validation/deployment?
1 voteThis feature was released on December 1st, 2020. Thank you for the suggestion.
-
ci owner
Allow CI jobs to be reassigned to new owners. Or allow for out of office functionality when CI Owner is out of office.
1 voteCompleted on March 6th, 2020 see documentation on https://docs.gearset.com/en/articles/3758806-transferring-ci-job-ownership
-
Functionality to Data Deploy Active Orders
Salesforce doesn't support the creation or update or standard Order records with a Status Category of Active. This means Gearset is unable to data deploy any active orders. It would be very useful if there was an option for Gearset to temporarily set active orders to a draft status for the deployment or the Order Records and related Order Records, and then set the status back to Active for the final step.
4 votesYou are now able to dow this with Gearset Data deploys
-
Add friendly Name to Deployment detail and be able to add/edit from that page
It'd be great to see the "Friendly Name" in the Deployment Summary page.
e.g. https://app.gearset.com/finished?deploymentId=XXXXXXXXX
And to be able to add/edit the Friendly Name on that page, same as it can be done in the Deployment Summary.
Our use case: We audit all our deployments to make sure they have a name. It would be very helpful to be able to send a Deployment Summary link to a user to tell him to add a name if it's missing.
5 votes -
Ability to create Pull Requests for AWS CodeCommit
Gearset can create Pull Requests for many of the source control systems that it integrates with, but not AWS CodeCommit.
As AWS users, it would be very useful to use to have this ability so that we didn't need to switch systems to create Pull Requests.
3 votesThis functionality was implemented in February 2022.
-
Add "Show selected" button to the Custom Filter editor
This button needs to be in the type and items columns. This way the developer will see the already selected components and be able to check faster if everything required is selected
1 vote -
User Last loggged in and User Usage
It would be great to see when a team member last logged in on the user account management page. It would also be great to see like a report or extension on the user page where we can see user usage information. Like number of compares, deployments, etc.. may when last compare was done.
23 votesTeam owners on the Automation Enterprise plan can find the last login time for each user in the CSV export on their account page.
-
1 vote
This is already supported as a [Named Item] under the [Setting] metadata type. Contact us in the in-app chat if you have trouble locating it.
-
Require Jira Ticket Before Validation or Deployment
We would like the ability to make the "Jira updates" section required (i.e. ticket selected) prior to validation or deployment.
2 votesYou can now require team members to link a Jira ticket before manual deployments and validations.
Simply, navigate to My Account -> Deployment Settings and enable the 'Require Jira Tickets' option.
-
Add support for the WorkSkillRouting metadata type
WorkSkillRouting is a key object in the configuration of Skills-based Routing for omni-channel (using Attribute Setup, not apex class), please add support for this object to enable comparison and deployment.
6 votes -
Include support for new metadata type 'PermissionSetGroup' (Winter '20)
As feature has moved from pilot to beta in Winter '20 release, looking for support in differencing and deploying the new 'PermissionSetGroup' metadata type.
20 votesYou can now deploy permission set groups in Gearset!
PermissionSetGroup isn’t included in the default metadata filter, so you’ll need to include it in any comparison filters you’re using.
Please get in touch if you spot any problems.
Thanks,
Tom
- Don't see your idea?