1469 results found

1. Allow us to personalize the report generated at the end of the deployment

   I want to send the automatic report generated at the end of the deployment to my client. However, I want to personalize it with the logo of my company or add additional text.

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployment automation  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Namespace Mapping for Managed Packages

   We are an ISV partner with a managed package we sell to lots of customers. That means our package is namespaced. However with a distributed development team and multiple dev orgs, all source code is not namespaced, and is maintained in source control (github) without namespaces. Only upon unit test and promotion to the package org, does the namespace get added. This results in two basic problems (and others). 1) comparisons between unit test and package result in almost everything being flagged as "changed" due to the namespace, and 2) all aura components are always flagged as "new" when they are not.

   All this means comparisons for managed package development are difficult and you must be very careful when deploying, which almost defeats the purpose of a tool like Gearset.

   We really need some better management of namespaces, specifically for ISV partners, so that comparisons are better indicative of true changes between dev/test orgs and the namespaced package org.

   We are an ISV partner with a managed package we sell to lots of customers. That means our package is namespaced. However with a distributed development team and multiple dev orgs, all source code is not namespaced, and is maintained in source control (github) without namespaces. Only upon unit test and promotion to the package org, does the namespace get added. This results in two basic problems (and others). 1) comparisons between unit test and package result in almost everything being flagged as "changed" due to the namespace, and 2) all aura components are always flagged as "new" when they… more

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Comparisons and difference visualization  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Static Code Analysis for JavaScript Components

   It would be great if Gearset could run static code analysis on JavaScript as well as Apex when deploying Lightning Components.

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Problem analysis and deployment failures  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Extend Jira Cloud Integration to Releases and Bitbucket

   We do the majority of our management via Jira and have it linked to Bitbucket and our test system so that we can manage everything via Jira. It would be great to extend the current integrations to more intelligently link the package to Jira tickets and the corresponding Bitbucket code and then push back to Jira the deployments in a more Jira friendly manner e.g. potentially creating/updating a Jira release for the deployment.

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Automated User Test Suite Integration

   Such as Selenium and/or Cypress.io

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Testing  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Save previously entered comparison filters

   I am currently using a standard regex filter each time I do a comparison. It has become quite lengthy such that I can't easily remember it. I have ended up saving it in a separate text file and have to open it, then copy and paste it into Gearset each time I do a comparison. Pretty cumbersome.

   It would be nice if the Filter... text box on the comparison results screen was a combo box that when clicked, dropped down a list of recently used filters. Each entry in the list should be removable (like with a little 'x' icon next to it).

   I am currently using a standard regex filter each time I do a comparison. It has become quite lengthy such that I can't easily remember it. I have ended up saving it in a separate text file and have to open it, then copy and paste it into Gearset each time I do a comparison. Pretty cumbersome.

   It would be nice if the Filter... text box on the comparison results screen was a combo box that when clicked, dropped down a list of recently used filters. Each entry in the list should be removable (like with a little 'x' icon… more

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  Comparisons and difference visualization  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Chatter posting to

   I think it would be useful if Gearset had the capability to make a chatter post to a specific group or @mention someone.

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Provide a way to init a sandbox

   It would be nice if there was a quick way of init'ing a new sandbox that matches either what was in source control or an existing sandbox.

   Currently, I need to run a comparison between the existing source and the new sandbox and then I can try the deploy, but it would be nice if the compare step was not needed and I could simply say 'overwrite what is in the sandbox with what is in the specified source'

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Deployment automation  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Differentiate XML and Code differences in the comparison

   I would find it very useful if the comparison result highlighted if the difference was in the XML or the Code (or both) for each item. This would especially save time when there are a lot of differences.

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Comparisons and difference visualization  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Under review  ·  AdminGearset Team (Feedback Manager, Gearset) responded

   Thanks for the suggestion Celio.

   We think this should be possible to do and are doing some background work into how to manage and display this. More details to come soon.

   Thanks,
   Jason.

10. Add ability to exclude specific files/folders of repo from a compare with source control

    Currently, if you try to compare a repository to a Salesforce org, it will throw an error with only the ability to send a report to Gearset if the repository contains files that are not compatible (gulp files, package.json, etc. at the root of the repo or any folder that isn't corresponding to a Salesforce type of file).

    My suggestion would be to add the ability for the user to exclude those files or folders from the compare and retry when it fails. This issue currently prevents us to use source control in the comparisons.

    7 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Ability for custom masking on Email fields

    Would love to be able to customize masking on email fields. When I currently mask an email field Gearset will make it something like 3d50b95f686844c6@gearset.invalid and I have no control over customization. I want to retain what the original email was so users can fix it and sent to it, if needed. I just want the email “broken” so it’s not used accidently through automation. Being able to customize the obfuscation would be very useful.

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Data deployment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Option to Export Full Comparison (Including JSON Metadata Differences)

    Currently, when exporting a comparison from Gearset, the CSV includes a list of all items from the comparison. However, the export does not include the JSON data that represents the metadata differences between environments.

    It would be extremely useful to have the option to export the full comparison, including the detailed JSON metadata diff.

    Use case:
    Our team is exploring ways to automatically generate changelogs whenever we make deployments. Being able to export the JSON comparison data would allow us to feed that information into an AI agent to generate a structured, human-readable changelog.

    Proposed enhancement:

    Add an option to export the full comparison data (including JSON metadata diffs).

    Ideally, make this available via both the UI and the API.

    This would open up powerful automation opportunities for teams looking to improve deployment transparency and release documentation.

    Currently, when exporting a comparison from Gearset, the CSV includes a list of all items from the comparison. However, the export does not include the JSON data that represents the metadata differences between environments.

    It would be extremely useful to have the option to export the full comparison, including the detailed JSON metadata diff.

    Use case:
    Our team is exploring ways to automatically generate changelogs whenever we make deployments. Being able to export the JSON comparison data would allow us to feed that information into an AI agent to generate a structured, human-readable changelog.

    Proposed enhancement:

    Add an option to… more

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Comparisons and difference visualization  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. View Deployment Summary from Pipelines

    My team develops in siloed dev orgs. Once a feature is complete, we create a PR against an integration environment.

    This triggers a test suite run in the target org and a peer code review. This process works well for Apex. However, admins on our team build automations in Flow, which are nearly impossible to review in GitHub due to the complexity of the XML.

    To address this, we’ve been using Gearset’s Flow Navigator for Flow code reviews. Previously, it only took a couple of clicks to reach the Deployment Summary screen, and the Flow visualization made reviews much easier.

    After a recent UI update, accessing Flow visualizations now requires a longer, more manual click path:

    1. Click the environment and note the PR# for the Flow(s) to review.
    2. Go to CI Jobs.
    3. Expand the target environment.
    4. Locate the PR by number.
    5. Click Validation runs.
    6. Click View Summary.
    7. Click Back to results.

    That’s 6–7 clicks plus manual PR lookup. Much less efficient than before.

    Since Flows are a common part of development and Flow Navigator is a powerful review tool, it would make sense to add functionality in the Pipelines Open PR screen to quickly view branch contents and Flow visualizations directly in Gearset.

    My team develops in siloed dev orgs. Once a feature is complete, we create a PR against an integration environment.

    This triggers a test suite run in the target org and a peer code review. This process works well for Apex. However, admins on our team build automations in Flow, which are nearly impossible to review in GitHub due to the complexity of the XML.

    To address this, we’ve been using Gearset’s Flow Navigator for Flow code reviews. Previously, it only took a couple of clicks to reach the Deployment Summary screen, and the Flow visualization made reviews much easier.

    … more

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. 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 that the deployment set remains up-to-date with the latest fixes and optimizations.
    User Satisfaction: Provide a smoother user experience by minimizing repetitive tasks and enhancing workflow continuity.
    This enhancement would greatly improve the usability and effectiveness of the Problem Analyzer tool.

    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… more

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployment automation  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Automate Jira Status when a Pull Request is created in Pipelines

    Presently, the capability to automatically update the Jira Status of a ticket is limited to transitions occurring between different environments in Pipelines. Enhancing this functionality to include automated updates triggered by the creation of a Pull Request would prove beneficial, eliminating the need for manual intervention when transitioning to stages such as "Code Review."

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployment automation  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Delete feature branches in Github in a way that they can be restored

    I closed a PR to master, and Gearset deleted the feature branch. However, it wasn't merged, so I wanted to restore it to continue work. I was completely gone from Github. I believe Gearset should do a normal delete that allows restoration instead of completely obliterating feature branches or allow an option to do so.

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Share edit access to a CI job with another user

    Currently, only the owner of a CI job is able to edit it. This is a risk, as the owner is not always available to troubleshoot CI issues. It would be helpful to be able to delegate edit access to other team members so that pipelines can be managed collaboratively.

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Deployment automation  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Expand the options for "Run job" times on the continuous integration job setup.

    Currently the "Run job" option has times for 1, 2, 4 and 24 hours. With international teams working on projects, it would be nice to allow for something like every 8 hours. That could either be a new set option in the list, or allow for a "custom" option. If the pipelines can handle between 1 and 24 hours, let us selection "custom" and input the hours for the job interval to run.

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Deployment automation  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. ClickUp integration would be awesome!

    My company uses ClickUp to manage tickets, would be great if there was integration with Gearset as that would save me copy/pasting ticket references into the deployment descriptions.

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Incorporate Relationship Graph into metadata deployment

    Right now is it not possible to deploy Relationship Graph metadata according to https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_relationshipgraphdefinition.htm with Gearset. This metadata is required for the so called Actionable Relationship Center, which is part of Financial Services Cloud. Even though the meta data is available in the Vlocity filter in Gearset, the items we are looking for doesn't fall under that one. If selected, no meta data get retrieved and therefore no deployment happens.

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating