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.

I suggest you...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

1292 results found

  1. Add ability to clone deployment CI job to validation-only CI job

    This would save us time duplicating regex statements for the new job

    6 votes
    0 comments  ·  Deployment automation  ·  Admin →
    How important is this to you?

  2. Allow CI jobs to validate PRs of a branch into Separate Scratch Orgs

    Currently CI jobs can only validate PRs into a regular org. So if you have multiple PRs raised to that branch then you have to wait as they each run one after the other. If we could validate into separate Scratch Orgs instead then all the PR validations could run in parallel and it would speed up validation

    6 votes
    2 comments  ·  Deployment automation  ·  Admin →
    How important is this to you?

  3. Users should be able to specify test classes and save them to draft deployments

    Users should be able to specific and save test classes in the comparison stage so they can be saved in draft deployments. Seems like a waste of extra steps to unclick tests and select tests over and over as you work through a deploy.

    also when deploys are combined, they would get all the test classes, again, saving lots of time.

    6 votes
    0 comments  ·  New feature  ·  Admin →
    How important is this to you?

  4. Bash scripting

    Add support for bash scripting. This is one of the most powerful features of Jenkins and something that would make a huge difference in Gearset.

    6 votes
    2 comments  ·  New feature  ·  Admin →
    How important is this to you?

  5. Archive or hide Automation jobs

    On each of the Automation dashboard views (Monitoring, Unit testing, Continuous integration) it would be nice to have a way to archive or hide job. Often times previously setup jobs that are not active but would be good to keep for historical reference can clutter the dashboard.

    6 votes
    2 comments  ·  Monitoring and reporting  ·  Admin →
    How important is this to you?

  6. Don't change the first 2 rows of a metadata file in version control

    Usually a Metadata file retrieved from Salesforce starts like this:

    <?xml version="1.0" encoding="UTF-8"?>
    <PermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">

    So two lines, first with the version and encoding UTF-8 and second with the type of metadata.

    Now when GearSet does the deployment to version control, either from an Org or a Branch it uses this styling of the first row:

    <?xml version="1.0" encoding="utf-8"?><PermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">

    So everything on one line, with the encoding in lower case.

    I don't see a logical reason this should be different in the files and is then causing differences in the version control system.
    Thanks for looking into this.

    6 votes
    1 comment  ·  Bug  ·  Admin →
    How important is this to you?

  7. Options to pick only selected custom labels metadata for salesforce.

    Since the custom labels metadata can’t be picked individually, the Gearset compare and validate process would pull in all custom label changes. This would be a concern if we want to withhold any particular custom labels from being pushed to higher environment.

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

  8. API to provision users, assign users to connected organisations

    API to provision users, assign users to connected organisations

    It would be hugely benificial to us (60+ connected organisations, 25 employees working in teams for multiple clients at a time) if we could programatically provision/deprovision users and provide access to connected organisations via an api.

    At the moment this is error prone manual work that has to be done by someone with high level access (and as such is usually already short on time).

    6 votes
    0 comments  ·  New feature  ·  Admin →
    How important is this to you?

  9. track metadata filter changes

    Filters are shared by default. However, if someone changes the filter, I cannot tell what has been changed, who made the change or when it was changed. Ideally, I'd like a version history for each filter.

    6 votes
    0 comments  ·  New feature  ·  Admin →
    How important is this to you?

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

    6 votes
    0 comments  ·  Deployment automation  ·  Admin →
    How important is this to you?

  11. Suppress irrelevant Suggested Fixes when deploying to git

    The problem analysis comes up with a number of Suggested Fixes which may make sense for improving Salesforce deployments, but which are unproductive when applied to git deployments.

    For example, the suggestion to remove TASK.WHAT_NAME, or to omit Standard Objects, will only serve to create a git repo which is an inaccurate reflection of the source org. Each time we deploy to that git repo, we will continue to have the same changes to select or omit, since the repo is missing objects and fields from the source org.

    When the deployment target is a git repo, all suggested fixes…

    6 votes
    1 comment  ·  Problem analysis and deployment failures  ·  Admin →
    How important is this to you?

  12. Display the Filter used in the Comparison history screen

    It would be helpful in finding the right comparison to look at if you could see on the Comparison History screen which filter was used. It would also be helpful when looking at the comparison details to know which filter was used.

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

  13. Show Created By and Created Date when doing comparisons

    When looking at a comparison it shows changed by as a column, would be helpful for consultants to Show Created By and Created Date as well

    6 votes
    0 comments  ·  New feature  ·  Admin →
    How important is this to you?

  14. Add support for Azure DevOps issue tracking features such as Azure boards

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

  15. Allowing data deployments in CI jobs

    Allowing data deployments in CI jobs. So that configurations in third party apps and B2B Commerce can be deployed as part of CI.

    6 votes
    1 comment  ·  Deployment automation  ·  Admin →
    How important is this to you?

  16. Filter on selected items

    I want to quickly be able to identify components that have not been reviewed by only seeing unselected items in the "Changed items", "New items" and "Deleted items" top level filters.

    seeing the ones I have already selected slows down productivity and I have to scroll through them. If I want to see them I can always look at the "All items" section. This information is also available in the difference type column.

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

  17. Jira: ability to associate tickets during comparison

    Would like the ability to associate Jira tickets during the comparison process so that it can be saved to draft deployments and can continue to add as needed. Currently it appears you can only add Jira tickets after you have finalized all items for deployment.

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

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

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

  19. Provide the option to skip problem analysis

    Sometimes during a complicated deployment I need to try a few different strategies to get things to work. For example, I may need to just send up one piece or set of metadata up first.

    The problem is, each time I do this, I have to wait for problem analysis to complete, which takes a couple minutes. Normally during a deployment I do want problem analysis to run, but if I want to quickly send up a single object, I have to wait a few minutes while Problem Analysis runs, and the time waiting adds up.

    Maybe a quick deployment…

    6 votes
    1 comment  ·  Problem analysis and deployment failures  ·  Admin →
    How important is this to you?

  20. Integrate with Jenkins

    Build a Jenkins Plugin to integrate with Gearset that would allow triggering CI jobs and/or deployments.

    6 votes
    1 comment  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Admin →
    How important is this to you?
1 2 … 7 9 11 … 64 65
  • Don't see your idea?

Help us improve Gearset

Categories

Feedback and Knowledge Base

(thinking…)