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. More granular control over CI job schedules

    Currently, a CI job that deploys from a Salesforce Org to another org or source control can only be scheduled to run at 4 hours intervals. Additionally, there is no mechanism of specifying when these jobs will run - instead, the job is scheduled randomly within the first 4 hours it was created and every 4 hours after that point.

    Providing a smaller interval (ex. every 1hr) and/or more granular control over the job execution time seems like a common sense enhancement.

    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

  2. Allow CI to do a quick deploy

    Allow gearset CI to do a quick deploy either by default or via a setting on the Job definition.
    Our tests run for nearly 90 minutes and are currently run twice in succession causing a lot of frustration. Once when a PR is validated and then when it is merged and deployed.

    19 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

    This functionality is now enabled automatically for CI jobs with the "validate pull requests targeting the branch" feature. This means Gearset will automatically try to quick deploy the package after the PR is merged meaning that tests don't need to be re-run. There is no need for users to change behavior and CI jobs will run and look as normal

  3. Make fail job optional for warning PMD analyses

    As a developer leader, I don't want the job to fail if I get a warning from PMD. But I want to be notified if the code has any warning.
    I would like the failure for warnings to be optional. But always be warned that it has flaws.

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

  5. Option to group and show all selected items while creating new custom filters

    Option to group and show all selected items while creating new custom filters

    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

  6. Prevent Deployments from Including LiveChatButton with Omni-Channel Routing

    https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_livechatbutton.htm

    LiveChatButton metadata that is routed using OmniChannel is not supported with the Metadata API and the deployment will fail.

    It would be great if Gearset had an analyzer to remove this for end-users to prevent the error.

    The following property is null for LiveChatButtons routed through Omni-Channel

    <routingType xsi:nil="true" />

    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

  7. Restore/export certain fields on objects

    We (the user) would like to be able to restore data, but only select certain fields to be restored.

    Usecase:
    A business user triggers some automation that modifies a field or specific fields on a large number of records that should not have been modified. In the meantime, other fields may have been modified that were correctly modified. We would want to restore a set of records from a specific backup, but only the specific fields that should not have been modified.

    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

    0 comments  ·  Data backup  ·  Admin →
  8. Search option when selecting a Data template

    When choosing a template in a Data deployment, an option to search all templates is needed. We will be updating/modifying/saving new templates often and a manual scroll will become inconvenient. Control F works to find a template, but a dedicated search option would be preferable

    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. Bitbucket pull request add Default Reviewers

    When using the "Create Pull Request" link on the deployment screen, please add the "Default Reviewers" to the BitBucket pull request.

    Currently we have to edit each pull request and add the reviewers manually.

    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

  10. Allow renaming of data deployment templates.

    It would be very useful to be able to see the details behind data deployment templates and manage / rename them

    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

  11. Default option for the deployment component list for JIRA issues

    I really like the feature to add a deployment component list to a JIRA ticket. I would like to have the ability to default this ON.
    It is currently defaulted to OFF.

    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 →
  12. CI Job notification email should report the actual errors directly instead of linking to CI Dashboard.

    This potentially can help the team to collaborate on the errors directly on Teams messages.

    For example, at present, the MS team notification says [A continuous integration validation job failed for validation job for PR # xx], but doesn't say which CI job name or what the validation/deployment error was.

    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

  13. Ability for team members to manually run the CI

    Currently, only the owner of the CI job can manually run the CI. If the owner is out or unavailable, this creates a problem for team members because they have to deactivate the current job, clone and setup the new CI OR transfer ownership. Transferring ownership doesn't work if a team member is out unexpectedly, ill or doesn't have access to perform the transfer.

    It would be helpful if you could grant access to a group of team members who have access to manually run the CI. This would save a lot of time and prevent having to keep multiple…

    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

    We have made changes to the app on the 29th of June release for Enterprise licensed Gearset users:

    Added the ability to run CI jobs belonging to other users if the source is a git repo and the target has deployment access delegated.

    We think this now covers the cases:
    - Allow an enterprise licensed user to run other people’s org to org CI jobs
    - Allow an enterprise licensed user to run other people’s git to org CI jobs

    We have not implemented allowing user to run other people’s org to git CI jobs. As this is sub use case is quite a specific interpretation of the original suggestion. Perfectly happy for it to be specified in another separate suggestion.

    We have updated the documentation to reflect this change – https://docs.gearset.com/en/articles/2533179-access-levels-in-gearset

    I hope this delivers the what your team needs. Feedback always welcome :)

  14. Validation job ownership should be transferred

    Good to have capabilities to transfer ownership of validation job to other member in the team so as if one person is on vacation then there should be easy way to transfer ownership of validation job to other member so as if required - Adjustment can be done to CI jobs.

    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

    Completed  ·  0 comments  ·  New feature  ·  Admin →
  15. Correctly create Price Book Entries records with different currencies and updated PBEs when they are out of sync (or delete+insert)

    1) Currently PBEs are incorrectly inserted with the company currency as apposed to the currency of the source record.

    2) PBE's currency cannot be updated once created (SF restriction) but because PBE's should not be referenced by Id, (that would be a terrible design decision). It is quite possible to delete and recreate any out of sync records.

    16 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

  16. To make it possible to abort started CI job on Continuous integration dashboard.

    At the moment, you need to wait until the comparison is finished and the deployment has been started and then you should go to the org to cancel running deployment. It would be useful to have an option to abort the CI job.

    11 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

  17. Ability to lockdown access to delete Deployment history

    It'd be nice if there was a way for admins to restrict access for devs/other users when it comes to deleting items from deployment history. The use case here is when a sprint is done and we're promoting changes from QA to UAT, it'd be nice to select all the sprint packages and combine them from deployment history so a user doesn't have to go through each change at a time. Providing full access to everyone opens the possibility for them to delete a package that should've been bundled with other packages on the promotion to UAT.

    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

  18. New Analyzer to prevent endpointURL changes for Outbound Messages in Sandboxes

    A major pain point and blocker to use automated CI jobs is that we cannot include workflow rules because we have outbound messages set up to specific test endpoints per sandbox/environment. As the workflow metadata type allows us no ability to filter by workflow rule name (it's by object), this means we have no option but to manually run the comparison and deployments for each of our sandboxes.

    It'd be great to add a problem analyzer to suggest not changing the endpointURL field on outbound messages when the target is a Sandbox. This way, you can deselect it manually when…

    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

  19. Enable Gearset login from corporate SSO solution

    an additional layer of security and convenience would be to enable Gearset login (that is, login to Gearset) to be done from an enterprise's SSO solution. We use Duo but Okta and others should be supported.

    Just like we can login to Salesforce from our enterprise's SSO , we should be able to login to related apps in our suite of enterprise tools via SSO

    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

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

  • Don't see your idea?

Feedback and Knowledge Base