Skip to content

Sunny Matharu

My feedback

2 results found

  1. 13 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)
    Sunny Matharu supported this idea  · 
    An error occurred while saving the comment
    Sunny Matharu commented  · 

    Encountering this very issue now. Surprised to see a suggestion from 2018 that has gone unaddressed. Equally surprised that it hasn't received more than 13 votes!

  2. 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)
    Sunny Matharu supported this idea  · 
    An error occurred while saving the comment
    Sunny Matharu commented  · 

    this is hugely important for us and impacts our ability to use gearset in all cases.

    it makes no sense for Agile development teams where there will be a mixture of object metadata in an org that is either ready, or in progress, where we only want to commit the "ready" sub-components.

    it also makes it practically impossible, without VSCode or direct repo mgmt to migrate a subset of object data from one company's org to another company's org (e.g. for mergers, subsisdiary companies etc)

    this is not a limitation of competing devops tools, and for all of Gearset's differentiating features, this is a huge blocker to adoption/transition.

Feedback and Knowledge Base