1394 results found

1. Show the Created Date and Refresh Date on the Draft Deployments

   I understand the Draft Deployments are snapshots from when they were created or last refreshed. Is that right? Please show these fields on the Draft Deployments page.

   3 votes

   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

2. Difference Viewer custom object name: include suffix __c, __x, __mdt, __e, etc

   When you look in the Difference Viewer, it is not clear at all by inspection which line of Metadata Type "Custom Object" is a standard object, custom object, platform event, custom metadata type, historcial trending object, etc.

   For example, Custom object Foo__c displays simply in the Name column as Foo. This is a loss of information in the difference viewer, especially if one has similarly-named custom object metadata types such as:

   Fooc
   Foose
   FooConfig__mdt

   these display as
   Foo
   Foos
   FooConfig

   The full Sobject Name gives the user hints as to perhaps other related components that need to be deployed (perhaps inadvertently omitted by the comparison filters) - such as layouts, permissions, custom metadata type values, etc.

   When you look in the Difference Viewer, it is not clear at all by inspection which line of Metadata Type "Custom Object" is a standard object, custom object, platform event, custom metadata type, historcial trending object, etc.

   For example, Custom object Foo__c displays simply in the Name column as Foo. This is a loss of information in the difference viewer, especially if one has similarly-named custom object metadata types such as:

   Fooc
   Foose
   FooConfig__mdt

   these display as
   Foo
   Foos
   FooConfig

   The full Sobject Name gives the user hints as to perhaps other related components that need to be… more

   3 votes

   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. Optimize comparison list view

   The comparison view contains a list view in a scrollable area with an line item for every metadata item in the comparison. Depending on the comparison, this list can be exorbitantly long (10k+ lines). Displaying this many elements on screen is extremely inefficient, and causes browsers to lock up when selecting the "check all" check box (because it results in thousands of incremental manipulations in the DOM). This issue also causes mobile browsers to crash when more than a thousand or so items show in the comparison results.

   There is a common pattern for handling long lists like this, in which a finite number of list items exist in the DOM. These list items are reused as a user scrolls through the list. Once a list item has scrolled far enough out of view, it is moved to the opposite side of the list, and its content dynamically updated to display the appropriate data for that index.

   The comparison view contains a list view in a scrollable area with an line item for every metadata item in the comparison. Depending on the comparison, this list can be exorbitantly long (10k+ lines). Displaying this many elements on screen is extremely inefficient, and causes browsers to lock up when selecting the "check all" check box (because it results in thousands of incremental manipulations in the DOM). This issue also causes mobile browsers to crash when more than a thousand or so items show in the comparison results.

   There is a common pattern for handling long lists like this, in… more

   3 votes

   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  ·  Bug  ·  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. Adjust dependancy on managed package versions for Apex[Class|Page]

   We've found when developing classes against managed packages the class ...meta.xml includes the package version numbers. Problem is these are fixed to the exact version installed (e.g. 9.4, 9.3 etc. example below)

   But then if the managed package is upgraded Salesforce, in its infinite wisdom, doesn't update these so when you come to deploy next time you have to go and manually update all the version numbers - or if you have a different version in another sandbox (to test the newer one) same thing.

   Seems like something a cool deployment tool could handle and offer to fix up on deployment.

   <ApexClass xmlns="http://soap.sforce.com/2006/04/metadata">
   <apiVersion>41.0</apiVersion>
   <packageVersions>
   <majorNumber>9</majorNumber>
   <minorNumber>4</minorNumber>
   <namespace>foo</namespace>
   </packageVersions>
   <status>Active</status>
   </ApexClass>

   We've found when developing classes against managed packages the class ...meta.xml includes the package version numbers. Problem is these are fixed to the exact version installed (e.g. 9.4, 9.3 etc. example below)

   But then if the managed package is upgraded Salesforce, in its infinite wisdom, doesn't update these so when you come to deploy next time you have to go and manually update all the version numbers - or if you have a different version in another sandbox (to test the newer one) same thing.

   Seems like something a cool deployment tool could handle and offer to fix up on… more

   3 votes

   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  ·  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

5. Integrate with Checkmarx for static code analysis
   3 votes

   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

6. Indicate whether a Validated Package is enabled for Quick Deploy

   T0 - You Validate a package to PROD (run all tests)

   T1 - You or someone else does a deployment of something else, no matter how minor, to PROD.

   T2 - You click Deploy of the Validated Package from T0, all the apex tests are rerun. This is by design per SFDC yet Gearset doesn't tell you in advance that Quick Deploy is not available. Something you think will take a couple of minutes now takes 30 minutes or more. You think you screwed up or Gearset is broken

   Suggestion: On Validated Packages page and on the page of a specific validated package, display a warning that a subsequent PROD deployment has occurred since the package was validated and that Quick Deploy is not available. This will help set expectations.

   T0 - You Validate a package to PROD (run all tests)

   T1 - You or someone else does a deployment of something else, no matter how minor, to PROD.

   T2 - You click Deploy of the Validated Package from T0, all the apex tests are rerun. This is by design per SFDC yet Gearset doesn't tell you in advance that Quick Deploy is not available. Something you think will take a couple of minutes now takes 30 minutes or more. You think you screwed up or Gearset is broken

   Suggestion: On Validated Packages page and on the page of a… more

   3 votes

   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

7. When a Picklist Populates, Don't Default to the 1st Value, Default to Blank

   When I choose my destination, the system defaults the picklist to the first item on the list. Instead it should populate the list but don't pick a value.

   For example, when I choose destination = BitBucket, it then takes a moment to load available branches. It takes a little bit so I go on and start to configure the metadata types. Meanwhile, Gearset populates the list and sets the value to the 1st branch on the list, in my case, feature/helpdesk. It should leave the value blank and make me pick.

   This has resulted in me running long-running comparisons, and even deploying to, the wrong organization.

   When I choose my destination, the system defaults the picklist to the first item on the list. Instead it should populate the list but don't pick a value.

   For example, when I choose destination = BitBucket, it then takes a moment to load available branches. It takes a little bit so I go on and start to configure the metadata types. Meanwhile, Gearset populates the list and sets the value to the 1st branch on the list, in my case, feature/helpdesk. It should leave the value blank and make me pick.

   This has resulted in me running long-running comparisons, and… more

   3 votes

   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

8. Show # differences found in comparison display

   It would be a nice feature to see the number of differences for each item from the perspective of the source org vs target org.

   3 votes

   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

9. Simple visualization showing Process Builder differences

   Assuming the high-vote count Idea for matching on latest version Process Builder flow between source and target (and not by version #) is implemented; make the visual comparison between source/target PB not solely XML.

   Process Builder in XML can't be deciphered by a human mind. Hence, a simple indented text-based visualization could be done to make it more readable

   1. Decision 1.1 Entry criteria 1.2 Immediate actions 1.2.1 action 1 details (XML here OK) 1.2.2 action 2 " " 1.3 Scheduled actions 1.3.1 scheduled action 1 (XML here OK) ...
   2. Next decision ...

   There's an implicit tree layout in the PB visual editor, need something to mimic that in gearset and color code diffs (red/yellow/green)

   Of course, mimic'ing the graphical view in SFDC or something like it would be even better

   If you want a system wherein there is a way to be sure your PB changes aren't smashing the target in an unexpected way; this is essential.

   Doing the same for Visual Flow is harder is the layout is arbitrary so let's start with PB (something more prevalent in orgs than VisualFlow)

   Assuming the high-vote count Idea for matching on latest version Process Builder flow between source and target (and not by version #) is implemented; make the visual comparison between source/target PB not solely XML.

   Process Builder in XML can't be deciphered by a human mind. Hence, a simple indented text-based visualization could be done to make it more readable

   1. Decision 1.1 Entry criteria 1.2 Immediate actions 1.2.1 action 1 details (XML here OK) 1.2.2 action 2 " " 1.3 Scheduled actions 1.3.1 scheduled action 1 (XML here OK) ...
   2. Next decision ...

   There's an implicit tree layout in the PB… more

   3 votes

   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

   Under review  ·  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

10. Deployment of pre-valided package doesn't include accurate test counts

    We did a deployment last week and noticed that as part of the deployment report that went out that it stated the Tests Run was zero. We did a pre-validation the day before where we ran all tests with all passing.

    Could this test section on the deployment report again include/include the pre-validation tests that were run for the deployment?

    3 votes

    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  ·  Bug  ·  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. Filter out Custom Field differences based on Field Tracking History

    If the only difference in the field is that History Tracking is turned on, it would be nice to filter these results out.

    Running checks on our app with multiple customers, who all set history tracking differently, can create a lot of noise to filter through to find actual differences.

    3 votes

    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

12. False positives in managed code

    When I enable comparing managed packages (e.g. when I have added a field to a managed custom object), I get lots of false positives saying that there are differences in apex code.

    On the source org, the code is show as "(hidden)"; on the target it is shown as empty. And Gearset lists this as a change.

    Obviously, I know it's not a change, but it adds a lot of clutter to the comparison view.

    3 votes

    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  ·  Bug  ·  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. Compare org monitoring from an arbitrary date to the current state of the org

    In Monitor ORG's tab, we have a daily set of cached metadata that can be used to troubleshoot issues in an ORG. This is great that we have this data. What would be even better (if there is not a way to do it currently), is if we could take the metadata cache from the monitoring job, "x" days ago, and compare it to the current state of an ORG.

    Maybe an ideal way to achieve this would be to select a cached version in the Compare Organizations screen. Alternatively, a button can be added in the Monitoring Job history list (for each row item) to compare cache to current.

    Please share your thoughts.

    Thanks!

    Richard Scott

    In Monitor ORG's tab, we have a daily set of cached metadata that can be used to troubleshoot issues in an ORG. This is great that we have this data. What would be even better (if there is not a way to do it currently), is if we could take the metadata cache from the monitoring job, "x" days ago, and compare it to the current state of an ORG.

    Maybe an ideal way to achieve this would be to select a cached version in the Compare Organizations screen. Alternatively, a button can be added in the Monitoring Job history… more

    3 votes

    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  ·  Monitoring and reporting  ·  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. A count of differences could be grouped by type

    If the count of differences could be grouped by type/color that would be helpful.
    Ex: 20 differences: 5 red, 7 green, 8 yellow. It gives a better sense of how drastic the differences between Source and Target are at first glance.

    3 votes

    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

15. On an unsuccessful validation, allow me to easily retrieve offending test classes so I can re-validate quickly.
    3 votes

    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. Add Webhook Error Logging and History for Outgoing Webhooks

    When configuring outgoing webhooks (e.g., to GitHub Actions or Slack), errors and failures are not surfaced to the user, making troubleshooting difficult and time-consuming. Currently, after a webhook is triggered (or fails to trigger), there is very limited visibility into what payload was sent, what response was received, or whether an error occurred. If a webhook fails silently or returns an error, I have no way to view detailed logs or the history of webhook attempts. Furthermore, error messages (if any) seem to clear out whenever CI job settings are saved, and there is no persistent record of webhook activity.
    This "blind debugging" increases the time and frustration required to resolve issues.

    Proposed Solution:

    Implement a persistent, searchable log or history for all outgoing webhook events in Gearset CI jobs, including:

    Timestamp of every webhook trigger (success or failure)
    Payload sent (with sensitive fields masked)
    Response code and body from the target endpoint
    Detailed error message if the webhook fails to send or receives an error
    Ability to manually re-trigger a webhook for testing
    Optionally, retain recent webhook logs even after CI job settings are updated

    This would empower users to quickly debug integration issues, validate payloads, and confirm that notifications and actions are working as intended. Having a clear audit trail of webhook activity

    When configuring outgoing webhooks (e.g., to GitHub Actions or Slack), errors and failures are not surfaced to the user, making troubleshooting difficult and time-consuming. Currently, after a webhook is triggered (or fails to trigger), there is very limited visibility into what payload was sent, what response was received, or whether an error occurred. If a webhook fails silently or returns an error, I have no way to view detailed logs or the history of webhook attempts. Furthermore, error messages (if any) seem to clear out whenever CI job settings are saved, and there is no persistent record of webhook activity.… more

    2 votes

    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  ·  Monitoring and reporting  ·  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. Mobile Support

    Support mobile devices.

    The CSS Used for the Pipeline Environment popover prevents the browser from scrolling horizontally. You can try this be logging into Gearset on your phone's browser or by narrowing the browser width on your desktop.

    1. I want to deploy from my phone.
    2. I want to monitor PRs from my phone.
    3. I want to browse my Scheduled Jobs and Monitoring Jobs.
    2 votes

    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  ·  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

18. Enable Excel export of org differences—profiles, permission sets, and objects—in the same side-by-side format with change indicators

    I compared two profiles from different orgs—specifically, the old and new environments of the same company—to identify any differences and present them to the client for review and approval of necessary changes in the new org. However, I was unable to export the comparison results into Excel. It would be extremely helpful to have the ability to export the comparison data in the same structured and visual format as shown in the Gearset comparison window, making it easier to review and share with stakeholders.

    2 votes

    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

19. Automate upstream branch syncing

    After merging/deploying to prod allow auto-creation of sync PR's to upstream branches/orgs (QA, UAT, Staging, etc...). If the sync PR's could be promoted automatically that would be amazing.

    2 votes

    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

20. Delete Flow by Version Number

    It would be beneficial to delete specific inactive flow versions. Examples where this would help streamline deployment changes:

    • You need to delete a custom field that is used in a flow. You create a new version of a flow, remove the dependency on the custom field and activate the new flow. Now you want to remove the flow version that still has the custom field dependency. Something like a checkbox to select the version(s) to remove.

    • You have inactive versions of a flow and you want to clean up the historic flow versions. Something like a checkbox to select the version(s) to remove.

    It would be beneficial to delete specific inactive flow versions. Examples where this would help streamline deployment changes:

    • You need to delete a custom field that is used in a flow. You create a new version of a flow, remove the dependency on the custom field and activate the new flow. Now you want to remove the flow version that still has the custom field dependency. Something like a checkbox to select the version(s) to remove.

    • You have inactive versions of a flow and you want to clean up the historic flow versions. Something like a checkbox to select the… more

    2 votes

    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