Skip to content

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.

If you need any further support, please contact us at team@gearset.com.

I suggest you...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

375 results found

  1. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Admin →

  2. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Data deployment  ·  Admin →

  3. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Deployment automation  ·  Admin →
    Completed  ·  AdminGearset Team (Feedback Manager, Gearset) responded

    Thanks 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.

  4. 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 selects

    12 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    4 comments  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Admin →

  5. Stop Reordering Package.xml

    We would like to keep our package.xml file in alphabetical/lexicographical order by the <type> element. Gearset appears to change the order so that datatypes that include all <members> elements (i.e. use an asterisk) are placed at the bottom of the file. This inconsistent sort order makes datatypes harder to find when viewing or amending the file.

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Comparisons and difference visualization  ·  Admin →

  6. Deployment screen to show which components were selected vs included

    When you get to the summary page, often times you will be deploying with the need for sub-components to be included in the package despite them being actual changes.

    When you're selecting those items inside the comparison page, it would be helpful to see that total be reflected in the deployment summary page. So if you picked 50 items to deploy but it needed an additional 1,000 components (despite them having No Difference) then we should see those breakdowns on the Deployment Summary

    Gearset soft alrt message "Some components with difference type of No difference have been added to the…

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Completed  ·  0 comments  ·  Comparisons and difference visualization  ·  Admin →

  7. Compare and Deploy Attachments and Files

    Please add the ability to use the "Compare and Deploy" for Attachments and Files. The ability to migrate PDFs, image files, word docs, and excel spreadsheets would be GREATLY appreciated! Thanks!

    19 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Data deployment  ·  Admin →

  8. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Deployment automation  ·  Admin →

  9. Ignore Unlocked Package Metadata In Comparisons

    Currently, metadata from Unlocked Packages show up when comparing against an org. This leads to duplication of metadata in source control repositories (correct DX package repository and incorrect monolithic, "happy-soup" repository).

    Using the Package2Member Object (Tooling API), it is possible to deduce whether or not a metadata item is part of an unlocked package. Therefore, it should be possible to ignore some or all unlocked packages (or any Package2 package), in a similar fashion to the way Gearset filters allow inclusion or exclusion of managed packages.

    17 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    9 comments  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Admin →
    Completed  ·  AdminGearset Team (Feedback Manager, Gearset) responded

    In comparisons, all metadata from unlocked packages is included by default. However, some users wish to exclude unlocked package metadata from a comparison. This is so that they don't have to see metadata that they don't need to consider for their deployment.

    So we’ve added this ability! 

    Within the packaging sidebar on the right hand side of the large filter, there is now an option to Exclude unlocked packages from a comparison. Shown in brackets is the number of distinct unlocked packages identified across the two environments.

  10. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Admin →

  11. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Completed  ·  1 comment  ·  Monitoring and reporting  ·  Admin →

  12. Ability to run a Validation only CI job on a pull request - this will make pull request ready for deployment without error

    1. Developer creates a pull request to a branch
    2. CI job validates the pull request and notify in case of errors
    3. Developer corrects errors - CI job again validates the pull request and this time it is fine 4.Release manager merges the pull request to the branch specific to an org and CI job deploys without error.
    9 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    9 comments  ·  Deployment automation  ·  Admin →

  13. Add Prompt metadata type

    Please add the new Prompt metadata type

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Completed  ·  1 comment  ·  Comparisons and difference visualization  ·  Admin →

  14. Dependency Enhancement for App Menu metadata

    Currently, when we compare App Menu metadata, the "Depends On" tree is empty, even though it definitely has dependencies on connectedApps and customApplications.

    Please add dependency analysis for App Menu metadata,

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Completed  ·  0 comments  ·  Comparisons and difference visualization  ·  Admin →

  15. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Admin →

  16. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Comparisons and difference visualization  ·  Admin →
    Completed  ·  AdminGearset Team (Feedback Manager, Gearset) responded

    When 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.

    More details: https://gearset.com/blog/smarter-salesforce-comparisons-that-hide-reordered-xml/?utm_source=twitter&utm_medium=social&utm_campaign=organic_post&utm_content=blog_smarter_salesforce_comparisons

  17. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Admin →

  18. Allow other Enterprise Users who do not own the CI Job to run it

    Enterprise Users can only "Run Now" Jobs that they own. If the Source and Destination Org are shared, allow other enterprise users to run the job.

    46 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Completed  ·  15 comments  ·  Deployment automation  ·  Admin →

  19. 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.

    https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/36198433-github-pull-request

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Deployment automation  ·  Admin →
    Completed  ·  AdminGearset Team (Feedback Manager, Gearset) responded

    Hi,

    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.

  20. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Comparisons and difference visualization  ·  Admin →
    Completed  ·  AdminGearset Team (Feedback Manager, Gearset) responded

    We'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!

1 2 … 6 8 10 … 18 19
  • Don't see your idea?

Help us improve Gearset

Categories

Feedback and Knowledge Base

(thinking…)