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.
360 results found
-
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 -
Add link to test results in Microsoft Teams
Please add a link to the test results as part of the notifications sent to Microsoft Teams. The integration with Slack already includes the link so it would be very helpful to have a similar integration in Microsoft Teams.
4 votesThanks for your suggestion. I am pleased to say that the Microsoft Teams test monitor notifications should now have feature parity with the Slack notifications.
-
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.
-
Separate Filters for CI Jobs to reflect filter edits
Currently, if you have a saved filter being used in CI jobs, any edits/changes to that filter are not reflected in the CI jobs that use said filter.
It'd be great if we could isolate filters for CI jobs so that we could edit CI job filters that would then affect every CI job they're being used with instead of having to edit every job and re-select the filter whenever a change is needed.
6 voteshttps://docs.gearset.com/en/articles/618760-custom-metadata-filters-in-compare-and-deploy-and-ci-jobs
-
CI dashboard: Show commitId when job is in flight; Show queued commitIds
On CI Dashboard page, a CI job in flight (deploying/validating) should show the commitId that triggered it (if any) PLUS show all pending CI jobs.
Reason: If two developers are sequentially merging to a shared branch tied to the CI org (and webhook is setup to run immediately), then the first developer's merge starts CI job 1 while the second developer's job is queued.
Yet, from the CI job page there is no way to even tell which commit to the branch is running (so as to clue the developer that his/her job is running vs queued. Commit message would…
3 votesThanks for the suggestion! When a CI job is running from git, the commit hash and the commit message is now visible for all git providers. In addition, for GitHub, Gitlab and BitBucket sources, a link to go to the relevant commit will be displayed.
-
Github Pull Request as a `Draft`
This new feature is great. Would be even better if you can select that the PR be a draft.
1 voteHi,
You’ll now see the option to create a draft pull request in GitHub, if your repository supports draft pull requests.
Draft pull requests are available in public repositories with GitHub Free, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see https://help.github.com/en/articles/about-pull-requests#draft-pull-requests.
-
Add Prompt metadata type
Please add the new Prompt metadata type
1 vote -
There should be an option to schedule unit test jobs weekly in Gearset
Hi Gearset,
I would suggest you to provide an extra option where we can select weekly ,daily or monthly schedule jobs in Unit Testing Jobs.Thank you,
2 votesYou can now choose which days of the week a unit test job should run, allowing you to schedule the job to run weekly.
-
List the unit tests failures in the email notification being sent out
Currently, when the unit test job fails, we can view the test history and results by going to the web page. However, we would like to view the summary of unit tests that failed in the email notification that is being sent out.
9 votes -
Add an option to disable the "repository sanitizer"
The "repository sanitizer" performs unsolicited/silently changes which confuse users and generate issues. For instance, if you have Apex class permissions in profiles for classes which are part of a managed package and are not present in the repository, this sanitizer will modify the permissions to false which is obviously a disaster, (and the changes can happen any moment, while users are trying to deploy something completely unrelated hence the confusion).
We know the solution is to have the classes also in the repository but for managed packages that's unnecessary extra work since then we need to be updating them every…
12 votes -
Optimize "Refresh Comparison" to only pull metadata that has been changed since the last comparison
Currently, clicking Refresh Comparison does not optimize the comparison in any way, it just allows you to skip selecting some of the configuration steps from running a new comparison.
This means that it takes the same amount of time actually comparing the orgs.
It would be nice if on clicking of "refresh comparison" the logic didn't run a full compare and instead just looked at metadata that had been changed since the last compare in order to reduce the comparison time.
21 votesHi everyone
We have now shipped the three key improvements to refreshing a comparison.
You are now able to:
- refresh a single item (right-click an item in the grid or use Refresh Item button in the Diff viewer)
- refreshing selected items (right-click a selected item in the grid)
- refresh only additional types in the filter (via Refresh comparison -> Filter dialog)
We hope these enhancements will greatly reduce the comparison time for you.
-
Report CI validation/deployment status to source control
When a CI job is triggered by a commit to source control, please update the source control system with the result of the build - so that e.g. with Bitbucket we could see the build result from pull requests as at https://confluence.atlassian.com/bitbucket/check-build-status-in-a-pull-request-945541505.html
4 votesGearset will now report CI job statuses to both Bitbucket and Bitbucket Server
-
Scratch orgs - Create a new scratch org with more than one package
During the creation of a scratch org the system doesn't allow the installation of more than one package...so after create a scratch org we need to install manually the remaining packages.
6 votesYou can now install more than one package when creating a scratch org.
-
Add batch size option to data deployment
It would be great to be able to pick the batch size used when doing data deployments.
We have to work with some orgs using poorly performing managed packages that are blowing up due to CPU limits.
We don't have many option, so being able to reduce the batch size, and hence the CPU load would be really useful.
8 votesThis now completed and can be set at a team level at https://app.gearset.com/account/data-settings
-
Unscramble order of <excludeButtons> tags in Layout metadata
Page Layouts use the <excludeButtons> element to indicate the presence or absence of standard buttons on a layout.
But this element appears in an arbitrary order when retrieved. Unlike other metadata which gets canonicalized by sorting alphabetically.
Gearset could sort these elements to avoid the random order causing random diffs to appear in metadata comparisons when in reality there is no difference.
4 votesWhen Gearset detects that the only differences in your Layout are the result of reordering, and so there aren't any real differences to show you, it will automatically consider this metadata to be unchanged. As a result, this Layout won't appear in the list of changed metadata and will no longer clutter up your comparison results.
If there are any material differences in your Layouts, they will still appear in your comparison results as normal.
And you'll be able to use the Hide reordering checkbox to filter out any immaterial differences, just as you would for other metadata types.
-
Add support for incoming webhooks
There's already a way to set up an outgoing webhook after a successful CI job run.
It'd be nice to have a way for a CI job to have an incoming webhook from another service, such as ElectricFlow (a build platform).
One use case would be for CI deployments to be dependent on external validation services.
4 votesThis is now possible since we have released our API, which is available to everyone with an Enterprise license! Please see https://docs.gearset.com/en/articles/6099550-getting-started-with-the-gearset-api for more details. If anyone has feedback or suggestions, please contact us via the in-app widget.
-
Allow deployments across managed package versions
Gearset does not allow comparisons or deployments of custom metadata on managed packages if the versions are different. We got ourselves in a situation where a package in the sandbox was a higher beta version that we couldn't upgrade to. This required us to do all the field deployments via changsets.
Adding a warning for deployments across managed package versions would be ideal as most changes one would deploy wouldn't necessarily cause any issues.
4 votesWe've added the ability to deploy across managed package versions using the Package Item Version Handling dropdown option within the filter sidebar.
If you have any feedback on this, please let us know!
-
Improve Bitbucket Server integration for teams with large number of project/repositories
ideally... gearset should not be hitting https://adlm.nielsen.com/bitbucket/rest/api/1.0/repos
first. It should hit https://adlm.nielsen.com/bitbucket/rest/api/1.0/projects to get a list of projects
then allow the end user to select the project
then https://adlm.nielsen.com/bitbucket/rest/api/1.0/projects/{projectKey}/repos to get a list of repos on the project the end user selects12 votesGearset will now filter by project first when selecting a repo/branch for Bitbucket Server
-
Introduce 'ListView' as an option in 'Metadata filter' tab
When navigating to the 'Metadata filter' tab to select filters, there are currently 122 options, however 'List View' is not one of them.
When navigating 'Metadata Types & Components' in Workbench, 'ListView' is described independently, and I have used it previously when deploying via ANT. Therefore I would imagine there is a way to identify List Views independently of 'Custom Objects'.
This would be a huge help with a Production monitoring job, as I do not mind if List Views are updated by certain users in Production, but currently they are flagged as differences. Basically, I want to ignore them…27 votesThis is now released, you will need to update the metadata filter for any jobs set up already to take effect.
You can now exclude list views as well as other subcomponents of custom object.
(Note: named items is not populated for subcomponent metadata types.) -
Warn user that clicking the "What's New in this version" will navigate away from the page they are on
The "What's New" toast for changes in Gearset looks like it will be a popup or overlay based on the UI, but when clicked actually navigates away from the current page.
1 voteClicking on the ’What’s new’ notification now uses a smaller notification pop-up about the latest changes and doesn’t navigate you away from the page you’re on.
- Don't see your idea?