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.
375 results found
-
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
-
Allow components to be added or removed from an data deployment template
Currently when a data deployment template is created, there is no way to edit the template after it is saved so that components can be added or removed. It would be helpful if we could modify the components in the template without having to create the template from scratch again.
21 votesThis has now been added. You can update an existing data deployment template by deploying from it and clicking on the save template modal on the data deployment summary screen.
-
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.
-
Remember default Bitbucket Server repo
According to https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/17292778-remember-a-default-github-repo, when one uses GitHub as a git provider, Gearset will remember the last used repo in a comparison.
However, this is not the case with the Bitbucket Server integration. Every time I do a comparison, I have to select the repository and branch again. With a large number of each, this is very tedious.
Please remember the last-used repo as a default, and do the same for the last used branch on that repo.
1 vote -
Stamp Deployment Results with Salesforce Id of the Deployment package for auditabilityq
When a deployment is successful, the deployment results/report should include the Id of the deployment package from Salesforce. This would create a foolproof audit trail between Gearset deployments and when they went into effect in Salesforce.
3 votes -
Update CI Job History Exports to include User and DateTime Stamp
In the CI Job section under the view history button, when selecting the ability to export the changes, Is it possible to include a DateTIme stamp
and User column for each row change?10 votes -
Update the CI Jobs Page so you can organize, similar to Deployments History page.
We have a bunch of CI Jobs, and it gets a bit difficult to identify whose job is owned by who just by looking at it.
Maybe make it similar to the Deployment History tab where I can sort out things by clicking the options above like "Owner" or "Name" and it'll organize it the way the Deployment History tab you guys have in place.
2 votes -
Allow Updating of Associated Jira Ticket Statuses on Successful Deployment
With Gearset's current the ability to associate a deployment with Jira tickets, and post updates as comments to the stages of deployments, the ability to choose the status (from what is defined in the status of the Jira Board), upon a SUCCESSFUL deployment, would be incredibly helpful in our environment plans for our projects.
By being able to select the status to update all tickets to from the Jira board, we could effectively manage our custom stages for different projects.
22 votes
- Don't see your idea?