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

1301 results found

  1. Unsubscribe from commit emails

    Choose to unsubscribe / subscribe from commit emails (success and or failures) in gearset setup in order to avoid generating unwanted emails (and their PDFs) for each deployment (and save a little CO2 along the way).

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Improve visualization of multiple features being simultaneously worked on in a single developer sandbox.

    Currently, one must select (or create) a single feature+branch in the developer sandbox. The pipeline view only shows 1 active feature at a time. It would be nice visually see all of the features an individual developer is working on/assigned to.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Gearset Pipelines Sandbox Environment

    In order to test new Jira webhooks, GitHub actions, and any other release management changes,

    We would like a Gearset sandbox environment where we could test release management changes like new/updates to Jira webhooks, GitHub actions, and other related changes.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Display pipeline webhook errors in Pull Request details

    Scenario:
    - Feature branch created, commits added, Pull Request opened and pushed part-way through the pipeline.
    - Pull Request has merge conflicts on one of the environments. Conflicts are addressed, but (let's say) PR fails validation so it is not promoted.
    - New commit is added to the feature branch.

    This commit will generally fail to propagate into the above mentioned PR branch (triggering a webhook error). It would be GREAT if that error were somehow displayed on the PR details screen.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Customizable Messages for Jira Ticket Associations

    When a Jira ticket gets a new comment from a validation or deployment, it's a pretty standard message:

    Deployment succeeded: link...etc.
    Deployment Notes:
    Source: ----
    Target: ----
    And then a table of differences that were pushed through.

    My thing is, none of this is customizable, whereas I'd love to be able to potentially change what's automatically appended to our tickets to make it more user-friendly for the reporters on those tickets.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Notifications for the errors in the webhook page on Pipelines page

    Add possible to configure notifications for the errors in the webhook in the Pipeline. Similar to CI Job notification. Ideally post to Slack

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Query for Deleted Records

    It would be helpful to have a way to query for all deleted records across multiple backup jobs for a specific object.

    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  ·  Data backup  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Allow tests to be run in parellel in multi orgs and allow aggregations of results for PR validation and speed up non prod deployments

    We get 100 sandboxes, Can create test orgs org1, org2, org3 where our unit tests are split and run in them so hour long tests just take 1/3 the time? We would like it to be part of our pipelines as of now PR validation to develop takes 40 mins which makes it unustainable.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Help to have a change log, including the name and email of the person who changed the test level in CI jobs?

    The test class level change in the job is crucial for us; if someone changes the test level to no test in place of a specific test run, components will go without a test run.
    So, if we monitor things on a regular basis, we can ensure that everything is in place.
    If we have a tab to get all these kinds of information, such as reports

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Gitlab Self Managed Issues

    We suspect that reading the 'weburl' response field for the specified branch from an API call to GET 'v4/projects/$projectid/repository/branches' might be causing a problem when using public Gitlab proxies.

    We suggest implementing a code change to compare the domain of 'web_url' to the self-hosted GitLab domain provided by the customers. The customer's self-hosted GitLab domain should take precedence.

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Set up notification according to the target connection we're deploying to.

    Set up notification according to the target connection we're deploying to. This way, the scheduled and manual deploys will notify us with what we set up.

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Allow deployment of 'Check For Matching Records' in Flows.

    As part of the new Salesforce Summer ’24 release, Salesforce have added the ability to check for matching records when using a ‘Create Records’ element. We’ve used this useful feature in various locations within our new flows to identify existing contacts for example.

    When deploying the flows using this feature between developer environments via Pipelines or Compare & Deploy in Gearset, we’ve noticed that this new setting within the element doesn’t get deployed and is switched off in the destination org.

    In the meantime, we can manually turn on this feature in the destination org.

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Save sort order in Saved comparison pairs

    It would be nice that the chosen sort order of the saved comparison pairs could be saved.
    If I choose to sort the saved comparison pairs on Friendly name and i open a new tab of gearset, the saved comparison pairs in the new tab are sorted on last used. It would be nice that in the new tab, the saved comparison pairs are sorted based on the same column as the previous tab.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Add an option to ignore API version differences during comparisons

    When comparing Apex, and other files with API versions the difference engine will mark any files with higher API version as "changed", even if the API version is the only change. This can be undesirable when there have been bulk updates to the API version that have not been made in the development environments. It would be great if the comparison engine could make it clearer when the only difference between two files is an API version (especially when the target is on a higher API version)

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Allow open PRs to queue up.

    Allow open PRs to promote via selection and to queue up against the target keeping blocking behaviour to just merges and the deploy activity

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Problem Analyzer should remove picklist values from record types when picklist values are removed from the picklist or value set.

    When removing or deactivating a picklist value, Problem Analyzer should remove these values from any record types that reference them. While the initial deployment of the picklist may succeed, subsequent deployments of the referencing record types will fail if they still reference a deactivated picklist value.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Picklist Comparison should show if value is active/inactive

    When comparing a picklist in which we have deactivated values, the simplified comparison visualization shows the deactivated values as being "added" (in green, on the source side).

    The XML reveals <isactive>false</isactive> is being added, but the simplified view seems to suggest new values are added instead

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. New, one-click "Promote" button is very risky

    In Deployment Pipelines when a PR for a CI Job is selected, a new, one-click "Promote" button exists, if the PR passes merge-conflict and validation checks. This new button is very risky in that it begins the promotion process, without recourse, when clicked.

    Perhaps that's the designers intent but for myself at least, the button is too easy to accidentally click out of inattention, distraction or mouse clumsiness and is especially risky in that I cannot recall the action.

    Personally I like the process of clicking the PR checkbox and clicking "Promote", which prevents unintended deployments.

    As an alternative to…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. audit report missing PR message

    The audit reports don't include much context of the deployment, which means they are pretty useless to us and do not serve our auditors' needs. Specifically, they do not include the PR message for deployments through our pipeline, which means we can't link each deployment to the specific ticket responsible for that deployment. The PR message is where we put our ticket. This information is needed for our SOX audit process. Additionally, we can not see a link back to the deployment, which would allow us to quickly reference the specific metadata files/components that were deployed.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Pre-fill Pull Request Description with comments from last commits

    In order to save time, when a Pull Request is created from the Pipeline, the Description field could be pre-filled with the comments from the last commits in the feature branch, instead of forcing the User to type something.

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base