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.

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

339 results found

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Testing  ·  Admin →
  3. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  4. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data backup  ·  Admin →
  5. 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 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bug  ·  Admin →
  6. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    In 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).

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Admin →
  8. 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 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  9. 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 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Completed  ·  0 comments  ·  New feature  ·  Admin →
  12. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  15. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Admin →
  16. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    You 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

  19. Allow users with owner role to modify and start backups

    Allow designated users the ability to modify and start backups without being the owner of the connected org or the person who created the backup.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data backup  ·  Admin →

    You can now specify other team members to have permissions to manage and start backup jobs they don’t own.

    The current owner of the backup job will need to edit the current job settings, go to the new ‘Permissions’ tab and choose the team member and level of access that you’d like to grant them to manage your backup job.

  20. 6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  New feature  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base