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.

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

347 results found

  1. Allow CI to do a quick deploy

    Allow gearset CI to do a quick deploy either by default or via a setting on the Job definition.
    Our tests run for nearly 90 minutes and are currently run twice in succession causing a lot of frustration. Once when a PR is validated and then when it is merged and deployed.

    19 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

    This functionality is now enabled automatically for CI jobs with the "validate pull requests targeting the branch" feature. This means Gearset will automatically try to quick deploy the package after the PR is merged meaning that tests don't need to be re-run. There is no need for users to change behavior and CI jobs will run and look as normal

  2. To make it possible to abort started CI job on Continuous integration dashboard.

    At the moment, you need to wait until the comparison is finished and the deployment has been started and then you should go to the org to cancel running deployment. It would be useful to have an option to abort the CI job.

    11 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

  3. Unique filename of the generated report PDF

    Currently, the name of the generated PDF file of the deployment report is always the same for a given source and target.

    If we deploy from our "master" gitlab branch to our "production" environment, the name will always be the same.

    We archive the report PDFs for documentation / compliance reasons, and we always have to manually rename the PDF file to make the name distinct.

    It would be nice if the name of the report PDF was unique. This could be achieved by either including a timestamp or the deployment number into the filename.

    1 vote

    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

    Completed  ·  0 comments  ·  New feature  ·  Admin →
  4. Update package.xml with destructive changes which helps CI jobs

    When I commit components to bitbucket brach if I have 5 new components and 5 deleted components. then Gearset is updating package.xml in the src folder with only 5 components which are to be created but destructive changes are tracked no where. Then if we deploy from this branch changes to Sandbox using CI job which has 'Filter metadata changes using package.xml' checked, then the deleted components will not be deployed. It is good if Gearset give a feature to track destructive changes and deploy using CI job.

    1 vote

    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

  5. Deploy CMS/CRM Connection and and CMS Collections

    We would like to be able to deploy CMS/CRM Connection and and CMS Collections. They are a part of Community Workspace.

    1 vote

    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

  6. Ability for team members to manually run the CI

    Currently, only the owner of the CI job can manually run the CI. If the owner is out or unavailable, this creates a problem for team members because they have to deactivate the current job, clone and setup the new CI OR transfer ownership. Transferring ownership doesn't work if a team member is out unexpectedly, ill or doesn't have access to perform the transfer.

    It would be helpful if you could grant access to a group of team members who have access to manually run the CI. This would save a lot of time and prevent having to keep multiple…

    14 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

    We have made changes to the app on the 29th of June release for Enterprise licensed Gearset users:

    Added the ability to run CI jobs belonging to other users if the source is a git repo and the target has deployment access delegated.

    We think this now covers the cases:
    - Allow an enterprise licensed user to run other people’s org to org CI jobs
    - Allow an enterprise licensed user to run other people’s git to org CI jobs

    We have not implemented allowing user to run other people’s org to git CI jobs. As this is sub use case is quite a specific interpretation of the original suggestion. Perfectly happy for it to be specified in another separate suggestion.

    We have updated the documentation to reflect this change – https://docs.gearset.com/en/articles/2533179-access-levels-in-gearset

    I hope this delivers the what your team needs. Feedback always welcome :)

  7. Export subset of data in data backup

    I would like to be able to filter what I want to export from a data backup, since I probably won't need everything from the database. This would make the downloading more manageable.

    Ex: Export only ContactID and Email fields from Contact object from a specific backup.

    (Restore data seems to allow this, but in this specific case I needed to run some checks in Excel since I couldn't just update everything with the old data)

    3 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

    1 comment  ·  Data backup  ·  Admin →

    You can now select the object(s) to export for a particular backup run.

    Simply go to the backup history for a job, and for a backup run, choose the ‘Download data’ option in the context menu to choose the subset of data that you’d like to export.

  8. Add support for the WorkSkillRouting metadata type

    WorkSkillRouting is a key object in the configuration of Skills-based Routing for omni-channel (using Attribute Setup, not apex class), please add support for this object to enable comparison and deployment.

    6 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

  9. Test Run results

    Test Run results show duration in Seconds but I believe the results are actually in Milliseconds

    2 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

    Completed  ·  0 comments  ·  Bug  ·  Admin →
  10. Correctly create Price Book Entries records with different currencies and updated PBEs when they are out of sync (or delete+insert)

    1) Currently PBEs are incorrectly inserted with the company currency as apposed to the currency of the source record.

    2) PBE's currency cannot be updated once created (SF restriction) but because PBE's should not be referenced by Id, (that would be a terrible design decision). It is quite possible to delete and recreate any out of sync records.

    16 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

  11. Add support for CMS Connect Sources

    Please add support for CMS Connect Sources in the comparison filters as well as the deployments and CI jobs.
    We're working with CMS Connect in our current developments of a customer community and we'd like to deploy this metadata as well.
    See the metadata api documentation: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_cmsconnectsource.htm

    2 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

    1 comment  ·  New feature  ·  Admin →
  12. Allow users with owner role to modify and start backups

    Allow designated users the ability to modify and start backups without being the owner of the connected org or the person who created the backup.

    5 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

    1 comment  ·  Data backup  ·  Admin →

    You can now specify other team members to have permissions to manage and start backup jobs they don’t own.

    The current owner of the backup job will need to edit the current job settings, go to the new ‘Permissions’ tab and choose the team member and level of access that you’d like to grant them to manage your backup job.

  13. Treat "New" FLS entries that don't grant any access as "Not Different" in Profiles and Permission Sets

    Due to a recent change in the SF API, Permission sets now display every field in the org as a "New" FLS item, with Readable and Editable both set to False. This is leading to two distinctly negative results.

    1) For every "Permissions for FieldNameXXX" item, every permission set in the org is modified. If two projects on two different sandboxes each add a field, they will both modify modify all the same files, and require manual XML merge. for our org thats almost 70 files that need manual merge with every new field.

    2) When you dig into a…

    3 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

  14. Allow Team Members to Run Scheduled Unit Test Jobs

    Execute Others’ Unit Tests

    John Doe creates daily unit test job for SuperHeros R Us. He schedules it to run nightly.
    Jane Smith, a member of the same Gearset team, is responsible for doing the weekly deploy for SuperHeros R Us. The unit test job from the previous day has failed (it had been previously working). Jane makes updates to the tests, and needs to re-run the unit test job. But she does not have permissions and John is out on PTO for the day. So… she needs to do it manually.

    14 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

    0 comments  ·  Testing  ·  Admin →
  15. Documentation around ramifications of deleting a connection (and possibly an Archive option)

    I haven't seen anywhere in the support documentation that details any ramifications (if any) when deleting a no longer needed Salesforce connection in GearSet.

    The kind of ramifications I'm thinking about are:

    • Validated Packages based on the connection, could I still review/clone/deploy?

    • Deployment History - will all information still be available? Can I still clone from a previous deployment?

    • Comparison History - can I pull up a previous compare?

    etc.

    If there is any negative impact to the above, then it would be appropriate to have an "Archive" option for Salesforce connections. The thought with this would be one, the…

    1 vote

    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

    Hi Jonathan,


    I have written a document detailing what happens when a connection is deleted. 

    You can view it here - https://docs.gearset.com/en/articles/7882840-deleting-an-org-connection.


    Thank you for your feedback and please do tell us if there is anything I've missed out.


    Quinn Kuiper

    Customer Success at Gearset

  16. Show start time, end time and duration of a data deployment

    This would be very helpful in order to communicate and set expectations with others on how long Data Deployments take as well as seeing how to improve the speed of longer running Data Deployments. If only one date/time can be displayed, then I think it would be better to see the End Time of the Data Deployment job. Currently, the Date column listed appears to be either (1) the start time of the Data Deployment job, or (2) the date/time when the Configure and deploy was clicked to start configuring the job. If it's #2, this isn't very useful.

    2 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

  17. Support the CustomHelpMenuSection metadata item

    We use the CustomHelpMenuSection item to customise our Help & Training dropdown list in Salesforce, and we would like to include it in our deployments automatically.

    It's been available in the Metadata API since version 45, but Gearset doesn't appear to support it yet.

    Will it be available soon?

    1 vote

    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

    Completed  ·  0 comments  ·  New feature  ·  Admin →
  18. Add Failure Information to CI Job's Email Notifications

    Currently, Unit Test jobs provide a nice email notification of what tests failed right in the email body.

    CI jobs, however, provides the same generic message for failures for validations as below:

    "The validation only CI job, Release Validation, has failed. Find and fix the validation issues on the error summary page in your CI job history"

    and for CI deployments

    "A continuous integration job, Prod to Dev3, has failed. No changes were deployed to the target org.

    Find and fix the deployment issues on the error summary page in your CI job history. "

    It'd be great to get…

    1 vote

    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

  19. 6 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

    2 comments  ·  New feature  ·  Admin →
  20. Support integration with OKTA

    Salesforce orgs that have OKTA as a SSO Identify Provider cannot seem to be connected to Gearset using SF Authentication. Therefore is makes it impossible to do Monitoring and Tests.

    Please look into supporting OKTA SSO

    2 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

  • Don't see your idea?

Feedback and Knowledge Base