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

1250 results found

  1. Remove "No Difference" items when commenting on jira tickets

    when i connect a jira ticket to a commit, I like the way gearset posts a comment on the jira ticket listing the changed items. what I dont like is the long list of "no difference" items posted on the ticket. It makes the ticket comments super long and annoying to scroll through. can gearset update this to only post the difference metadatas, or at least give us the option to include or exclude

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Please add support for decomposeCustomLabelsBeta

    Salesforce added the option to configure multiple features in the DX Project Configuration file. One of the is breaking down the big CustomLabels file into individual files where we no longer need to deploy the whole file but just a file (label) that has changes in. Please see SFDX Documentation here - https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_ws_config.htm

    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

    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)
  3. Provide the ability to get a deployment report on multiple deployment packages

    Instead of having to download the deployment report individually for multiple deployments, I would like to be able to select multiple deployments and download one report that contains a list of all files that were deployed as part of the multiple deployments. It is too cumbersome to manually download a report or .csv for each deployment and then copy/paste the info into one location so that I can get a comprehensive list of all files that were deployed.

    9 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Precision Deployments for Flow

    Please add Flow for Precision Deployment. The new flow visualization has been really great and it would be very helpful to be able to use precision deployments with them.

    18 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Add "Open Branches" Tab to Development Sandbox Environments in Pipeline

    The only way to deploy an existing feature branch into a development sandbox is to perform a manual compare and deploy. Previously, we had our developer sandboxes set up as static environments which allowed us to create PRs against them for "re-deploy". This is not possible with the new Development Sandbox format. I suggest another tab be added called "Open Branches" which will allow the developers to select a feature to pull and work on in their development environment. That way we get the benefit of easy compare & deploy instead of having to manually compare and deploy. This will…

    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

    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)
  6. It would be great to have a centralized way to view all components and static code analysis results for every commit within a branch.

    It would be great to have a centralized view for all components and static code analysis results across every commit within a feature branch. For example, if a developer makes five commits to the same branch, it would be much more efficient to review the components and static code analysis results for the entire branch in one place, rather than checking each commit individually through the deployment history. Additionally, there should be an export option to easily share the results with developers. Thanks

    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

    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)
  7. Visibility settings for 'Shared Sandboxes' in the gearset pipeline

    Currently, Gearset only supports the binary visibility settings for sandboxes; either the developer could see his/her sandbox or everyone's sandbox. But in the case of a 'Shared Sandbox,' there is no ability to give visibility access only to a specific subset of users in the pipeline.

    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

    1 comment  ·  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)
  8. Add the ability to use attachments (e.g Screenshot) in Pre/Post in GS Pipeline

    Adding the screenshots in Pre/Post deployments is very essential to streamline the deployments. Sometimes the steps could be complex and confusing, and if the build team could add the screenshots, then it will help the release team to execute those manual steps without the need to get in touch with the developer.

    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

    1 comment  ·  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)
  9. Please add support for GenAI objects

    Backups are currently failing when GenAI metadata objects are selected. Please add support so that we can backup agentforce related metadata.

    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. Allow users to choose their default comparison view

    Different types of Gearset user will prefer to analyse comparisons in different ways. Some will definitely prefer the XML view; others will prefer the new simplified views.

    I think it would be great if Gearset allowed users to specify their default view and comparisons load with this preference.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Dependency-Aware Deployment Sequencing in Gearset

    Currently, deployments in Gearset can fail when interdependent metadata components are deployed simultaneously without respecting their dependencies. For example, deploying a new Lightning page that references a report or dashboard will fail if both are included in the same deployment, as the referenced report or dashboard does not yet exist in the target org.

    While the current workaround is to manually split deployments into separate feature branches based on dependencies, a more intuitive approach would be for Gearset to detect these dependencies automatically when multiple related components are included in a deployment. The tool could then offer options to handle…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. add the name of the draft deployment somewhere on the comparison view

    Allow the user to be able to see the name of a draft deployment somewhere on the screen when in the comparison view. Often times, team member will share links to draft deployments but we have to follow up in order to find the actual name of it.

    Since the user is taken to the comparison view when they click on a draft deployment link, the name should be visible somewhere on that comparison view page. Even better if that name can also be copied to clipboard.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Add the ability to put CI jobs into folders

    It would be great if we had the ability to put ci jobs into folders. We've accumulated a number of CI jobs. Some of these jobs are no longer in service and we're a bit reluctant to delete them as they may have historical information that we may later want or need. It would be great to be able to put things like this into folders to help reduce clutter and organize our CI jobs page. thanks for your consideration.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Clickable Jira Request within Pipeline Promotion History

    I would like the ability within the pipeline promotion history to make the Jira tickets clickable. That way a user could simply click the ticket reference to navigate directly to the request.

    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. Deployment version control of Process Builders

    This is for Process Builders. Add a feature to allow users to select which version of the process builder to deploy. Similar to what is available for lightning flows. I realize that Process Builders are going away. However, this feature would be helpful as many orgs sill have to manage 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. jira comment after deployment

    Right now gearset posts comments to Jira when validation is completed and PR is merged.
    We would like to have comments also when deployment is completed.

    The current comment "Successfully merged PR #297 from gs-pipeline/SF-23601-preprod into preprod" tells nothing to business users, they are not aware of git, CI/CD and what this message means.
    Comment "Deployment to preprod is completed" makes much more sense for them.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. audit api user friendly interface

    The current process for finding deployments that included a specific component requires multiple steps including downloading JSON and working in a spreadsheet. It would be nice to have a UI that allows us to select a time frame and specific component API name and get a filtered list of deployment jobs within the given timeframe that included the given component.

    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)
  18. Create user friendly Audit API query process

    The current process for finding deployments that included a specific component requires multiple steps including downloading JSON and working in a spreadsheet. It would be nice to have a UI that allows us to select a time frame and specific component API name and get a filtered list of deployment jobs within the given timeframe that included the given component.

    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)
  19. Allow to export the data of an object or multiple objects for a specified time period

    Through the UI or through an API allow to specify the Object (it can be the API name of it) and a time period e.g. 01/01/2024 to 31/12/2024 and generate an export of all records for that object in a zip with independent CSVs with all the data of that 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)
  20. Save Problem Analyzer Changes to Deployment Set

    When using the Problem Analyzer to identify and fix issues within deployment sets, it's common to add or remove items to address specific problems. Currently, these changes are not automatically saved, which can lead to recurring issues in subsequent analyses.

    Suggested Enhancement:
    Introduce an option that allows users to save their modifications directly to the existing deployment set or create a copy of the set with these changes. This feature would streamline the problem-solving process and ensure that resolved issues do not reappear in future analyses.

    Benefits:
    Efficiency: Reduce the time spent on re-analyzing and re-fixing recurring issues.
    Consistency: Ensure…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 62 63
  • Don't see your idea?

Feedback and Knowledge Base