363 results found

1. Do not add Pre/Post Deployment if there is no value.

   The current behavior is when the developer do not have any Pre/Post deployment steps added in his/her PR even though Gearset adds the comment in VCS and Jira, and as a result, it creates lots of noise.

   Gearset: Deployment steps for UAT1 #4062 (do not edit)

   Pre-deployment steps
   Title

   Completed at

   Completed by

   Post-deployment steps
   Title

   Completed at

   Completed by

   7 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

   Completed  ·  0 comments  ·  New feature  ·  Delete…  ·  Admin →

2. 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.

   4 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

   Completed  ·  1 comment  ·  New feature  ·  Delete…  ·  Admin →

3. Add the ability to set Metadata filters for all Pipeline environments at once

   In order to update the metadata filters in a pipeline, one must individually update each environment's metadata filter from the list of Continuous Integration jobs.

   It would be amazing to be able to set a metadata filter in the pipeline and have it propagate to all environments in the pipeline.

   12 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  ·  Deployment automation  ·  Delete…  ·  Admin →
   Completed  ·  AdminGearset Team (Feedback Manager, Gearset) responded

   The way metadata filters work in CI jobs has been updated. Changes made to a shared custom filter will now apply immediately to all CI jobs where that filter is used. This means a single filter can be used to manage multiple CI jobs. Check our documentation for more information.

   
   

   To adopt this, head to your CI jobs, select the filter you need, and hit save in all of them.

   
   

4. Mask data that already exists in an environment

   At the moment, we know that you can mask data whilst seeding it into an environment. However, what we would like a way to mask data that already exists in an environment.

   A use case is that we have a full sandbox that contains customer data that we want to mask without needing to seed the data in first.

   It's a common use case for organisations that deal with 3rd party suppliers but do not want their customer data exposed to the 3rd parties. For instance, a Salesforce implementation partner is delivering a project. They need access to the environments to build and deploy but they don't need to see the customer data, which should be protected. The data already exists in partial or full sandbox so an admin just needs to mask personal identifiable data without needing to delete all the data to seed back into the environment

   At the moment, we know that you can mask data whilst seeding it into an environment. However, what we would like a way to mask data that already exists in an environment.

   A use case is that we have a full sandbox that contains customer data that we want to mask without needing to seed the data in first.

   It's a common use case for organisations that deal with 3rd party suppliers but do not want their customer data exposed to the 3rd parties. For instance, a Salesforce implementation partner is delivering a project. They need access to the environments to build 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

   1 comment  ·  Data deployment  ·  Delete…  ·  Admin →
   Completed  ·  AdminGearset Team (Feedback Manager, Gearset) responded

   Thanks for your feedback. We have now released In-place Masking! This feature allows you to mask existing data in a Salesforce sandbox. It can mask up to 9 million records per hour and comes with all the masking options you have come to expect from Gearset. You can find In-place Masking by navigating to the data deployment dashboard in the Gearset app. We'd love to hear any opinions you have on this new feature.

5. sidebar

   Love the comparison v2 but can there be an option to collapse the side bar with all the metadata types? When doing diffs sometimes I wish I could have the full width of the screen.

   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

   Completed  ·  0 comments  ·  Comparisons and difference visualization  ·  Delete…  ·  Admin →

6. Auto-scroll simplified comparison views to the first difference

   When you view a comparison using the XML view, Gearset automatically scrolls you to the first change in the XML file.

   However, when you use the simplified view, which is now the default comparison experience, it does not automatically scroll, and you either have to use the Next icon (an extra click every time) or do a lot of scrolling.

   I would like to request that the simplified comparison views also scroll to the first difference.

   1 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

   Completed  ·  0 comments  ·  Comparisons and difference visualization  ·  Delete…  ·  Admin →

7. Add omni components to filters through metadata API

   Now that Salesforce has moved omnistudio into standard runtime (as opposed to managed package) and also added the omnistudio components to the metadata API, the following components:
   omniDataTransform
   omniIntegrationProcedure
   omniScript
   omniUiCard

   Since these components are in xml format, it is much easier to see differences in source control.
   It also removes the need to perform separate deployments for the Salesforce metadata API and the vlocity build tool.

   7 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

   Completed  ·  1 comment  ·  Comparisons and difference visualization  ·  Delete…  ·  Admin →

8. UI improvement suggestion

   Hi, just a quick suggestion for improvement as someone who is using the Pipelines feature. Would really like to be able to get to the pipelines screen a lot easier - ideally with one click. Best case scenario is I can customize what I see in the left navigation panel and also choose to "pin" it. I've been a Gearset user for 7+ years and I still struggle to find what I need in that navigation panel. I think these features would make my life 10x easier!

   1 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 →
   Completed  ·  AdminGearset Team (Feedback Manager, Gearset) responded

   Hi AI Hotchkiss, thank you for the suggestion.

   Gearset lets you configure your homepage (My Account -> Profile Settings -> Homepage).

   You can choose "Deployment Pipelines" option in the drop-down to make Pipelines your homepage when logging to Gearset.

9. Conflicts between the Feature branch and Promotion branch as comments in the Github PR.

   Currently when there is a conflict between the feature branch and the promotion branch in Github- The Gearset Github app does not move new commits to the promotion branch. This totally makes sense but it is not obvious to a developer what is going on. I suggest that the Gearset app post a comment to the PR (or a message in the Github Check run maybe) that there is a conflict that needs to be resolved before new commits to the feature branch will propagate to the associated promo branches. Thanks!

   1 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 →
   Completed  ·  AdminGearset Team (Feedback Manager, Gearset) responded

   Thank you for your feedback! We’ve recently enhanced the process around handling conflicts between feature branches and promotion branches, specifically to address the confusion you’ve mentioned.

   
   

   Previously, when new commits are added to the feature branch:

   1. Gearset would attempt to merge the feature branch into the promotion branch.

   2. If conflicts were detected, Gearset would try to resolve them automatically using our custom git merge driver.

   
   

   What’s new:

   3. We’ve now introduced an additional safeguard. If the previous steps fail, Gearset will perform a forced reset of the promotion branch to match the feature branch. In addition, Gearset will post a comment on the Pull Request to explain the reset, ensuring full transparency.

   
   

   This update ensures that the promotion branch accurately reflects the latest changes from the feature branch at all times, and that developers are kept in the loop whenever an intervention occurs.

10. Add page "Saved comparison pairs" as a default landing page in account settings
    1 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

    Completed  ·  1 comment  ·  Team and account management  ·  Delete…  ·  Admin →

11. Webhook errors page does not have a scroll bar

    Firstly, thank you for adding the Webhook errors page! This surely will help us troubleshoot webhook issues. However, I am having an issue viewing the page.

    Steps to reproduce:

    Using Chrome or Edge, Windows 10
    Pipeline > Gear Icon > View Webhook Errors > Observe that there is no scroll bar on the side of the page, nor does scrolling with mouse work as expected, yet there's clearly additional rows partially displayed.

    1 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  ·  Bug  ·  Delete…  ·  Admin →
    Completed  ·  AdminGearset Team (Feedback Manager, Gearset) responded

    Hey,

    
    

    As of 3rd of April 14:00 UTC time, this has been fixed. 

    
    

    Thanks again,

    Gearset Team

12. Include duplicate rules in "Disable validation rules, triggers and flows"

    Here's a powershell script I hacked-up to do this from sfdx directories in vs code:

    $duplicateRules = ".\force-app\main\default\duplicateRules"
    $temporary = -join("duplicateRulessave",[System.Guid]::NewGuid())

    Save repository versions

    New-Item -ItemType Directory -Path $temporary
    Move-Item -Path $duplicateRules*.* -Destination $temporary

    Retrieve org versions

    sf project retrieve start --metadata DuplicateRule

    Make deactivated versions

    $files = Get-ChildItem -Path $duplicateRules -Filter "*.xml"
    foreach ($file in $files) {
    $content = Get-Content $file.FullName
    if ($content -match "<isActive>true</isActive>") {
    $content -replace "<isActive>true</isActive>", "<isActive>false</isActive>" | Set-Content $file.FullName
    } else {
    Remove-Item $file.FullName
    }
    }

    Deploy deactivated versions

    sf project deploy start --metadata DuplicateRule

    Restore repository versions

    Remove-Item $duplicateRules*.* | Where-Object{!($_.PSIsContainer)}
    Move-Item -Path $temporary*.* -Destination $duplicateRules
    Remove-Item $temporary

    $duplicateRules = $null
    $temporary = $null

    Here's a powershell script I hacked-up to do this from sfdx directories in vs code:

    $duplicateRules = ".\force-app\main\default\duplicateRules"
    $temporary = -join("duplicateRulessave",[System.Guid]::NewGuid())

    Save repository versions

    New-Item -ItemType Directory -Path $temporary
    Move-Item -Path $duplicateRules*.* -Destination $temporary

    Retrieve org versions

    sf project retrieve start --metadata DuplicateRule

    Make deactivated versions

    $files = Get-ChildItem -Path $duplicateRules -Filter "*.xml"
    foreach ($file in $files) {
    $content = Get-Content $file.FullName
    if ($content -match "<isActive>true</isActive>") {
    $content -replace "<isActive>true</isActive>", "<isActive>false</isActive>" | Set-Content $file.FullName
    } else {
    Remove-Item $file.FullName
    }
    }

    Deploy deactivated versions

    sf project deploy start --metadata DuplicateRule

    Restore repository versions

    Remove-Item $duplicateRules*.* | Where-Object{!($_.PSIsContainer)}
    Move-Item… more

    1 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

    Completed  ·  0 comments  ·  Data deployment  ·  Delete…  ·  Admin →

13. On the new Flow Comparison, goto connections incorrectly display as "End"

    When seeing the changes in a flow in the new graphic comparison, there are connections which are incorrectly displayed as the flow ending

    1 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

    Completed  ·  0 comments  ·  Bug  ·  Delete…  ·  Admin →

14. Improve the doc page: Fixing a feature that’s halfway through the pipeline

    The procedure as written seems complex and counter-intuitive

    Given that a developer sees the process as DEV->Integration->UAT, if an error is detected in UAT manual or automated testing, the fix should flow from DEV -> integration -> UAT.

    But the article has the fix going from DEV->UAT and then back propagations back to Integration plus manual PRs created in VCS. This seems way too complicated and hard to understand for a mere admin or junior dev

    1 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

    Completed  ·  1 comment  ·  Deployment automation  ·  Delete…  ·  Admin →

15. Add to Flow Navigator the flow version description

    It would be very handy if the new Flow Navigator view was able to display flow version description. We update this frequently to describe new changes, so being able to read this documentation in the Flow Navigator would be helpful to understanding the flow.
    Adding this either as a banner along the top (like some flow xml views) or as an element in the navigator sidebar would be acceptable.

    1 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 →
    Completed  ·  AdminGearset Team (Feedback Manager, Gearset) responded

    You can find the Flow description under "Settings" in the Flow Navigator sidebar

16. 'View and Resolve Conflicts' button should open in a new tab

    More of a UX enhancement than a bug but not sure where else to put this. From a PR in the pipeline, the 'View and Resolve Conflicts' does not allow me to open the page in a new tab (tried Chrome and Edge). It would improve my workflow quite a bit if it opened in a new tab by default, or at least gave me the option to right-click open in a new tab. The conflicts take a while to load and I almost always have something else to look at on the CI pipeline page while the conflicts are loading.

    More of a UX enhancement than a bug but not sure where else to put this. From a PR in the pipeline, the 'View and Resolve Conflicts' does not allow me to open the page in a new tab (tried Chrome and Edge). It would improve my workflow quite a bit if it opened in a new tab by default, or at least gave me the option to right-click open in a new tab. The conflicts take a while to load and I almost always have something else to look at on the CI pipeline page while the conflicts are… more

    1 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  ·  Bug  ·  Delete…  ·  Admin →
    Completed  ·  AdminGearset Team (Feedback Manager, Gearset) responded

    We've made a change so that you can right click the "View and resolve conflicts" button to open the page in a new tab.

17. Add ability to precision deploy custom applications and all other file types

    The ability to select specific lines in files for deployments is crucial for org and project management, and should be expanded to all file types. For example it currently is not possible to only deploy a new tab in a custom application, without deploying all other changes in that custom app, which is not manageable with multiple projects/updates being worked on that application concurrently.

    5 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 →
    Completed  ·  AdminGearset Team (Feedback Manager, Gearset) responded

    We've added precision deployments for Custom Applications 🎉

    
    

    Please get in touch if there's any specific metadata types that you'd like to see in precision deployments.

18. Allow automatic tagging of release commits

    I've found it very useful to be able to quickly identify release merge commits from our VCS. Being able to search for a tag in our VCS would allow us to easily compare one version to another without having to use something like git bisect. I'd like the option to automatically tag a commit (you could probably use the release name) would be helpful.

    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  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Delete…  ·  Admin →
    Completed  ·  AdminGearset Team (Feedback Manager, Gearset) responded

    Gearset will automatically tag pipeline releases with the release name. For more information check our documentation.

19. MetaData Type for BatchProcessJobDefinition missing

    The MetaDataType for BatchProcessJobDefinition is missing from GearSet's list.
    Need this added to allow us to deploy Batch Process Job Definitions between environments.

    https://developer.salesforce.com/docs/atlas.en-us.industries_reference.meta/industries_reference/meta_batchprocessjobdefinition.htm

    1 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 →
    Completed  ·  AdminGearset Team (Feedback Manager, Gearset) responded

    This was released 10th November 2023

20. Support OmniSupervisorConfig Metadata Type

    Can you please support OmniSupervisorConfig metadata type that was introduced in Spring '23 (API v57.0) as per the official documentation: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_omnisupervisorconfig.htm

    1 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

    Completed  ·  0 comments  ·  New feature  ·  Delete…  ·  Admin →