Help us improve Gearset
Welcome to the Gearset feedback forum. We love getting feedback from our users on how we can make Gearset even better.
Post your ideas and vote for others – let us know what’s important to you. We’re keen to hear about product improvements, new features, and bug fixes alike. We check this forum regularly and will keep ideas updated with their current status. If you need any further support, please contact us at team@gearset.com.
-
CI job status "deploying" - add dateTime
UX suggestion:
On the CI jobs page...Currently - you see last run dateTime followed by "deploying...." if a job is currently in progress
Suggestion: Add the dateTime when job started so user can gauge when job should finish and set expectations accordingly
For example, in our shop, a CI job should take around 20 minutes - but if you can;t tell when it started, you can't gauge when it will finish and plan your work accordingly
2 votes -
Enforce code coverage limits on CI jobs
Please set it so that we can force a code coverage check on deployments (including CI). I'd like to verify on the lowers before going through to production. Might be able to do this with test cases but should be able to on deployment.
2 votes -
Be able to switch the direction of a comparison/deployment
Sometimes we need to reconcile changes on an object between two orgs, where some of the changes have been made in Org1 and some in Org2. Having set up metadata filters, compared and deployed required changes from Org1 to Org2, it would be nice to be able click a button to switch direction to then deploy required changes from Org2 back to Org1, without having to go through the whole process of setting up a new comparison.
6 votes -
Scheduled deployment freezes
Prevent deployments during certain periods of time for a team or for production environments
8 votes -
Allow "Rollback" if you have a user within the same org
Rollback currently requires the user who did the deployment to enable "Deployment" user access. Instead, it would be helpful if I could use my own user, within the same org, to do the rollback.
This would be helpful if the individual who did the first deployment is unavailable.
3 votes -
Ability to copy Territory models from one org to another
It would be great to be able to copy Territory models from one org to another, as per this request in the SFDC Community...
https://success.salesforce.com/ideaView?id=08730000000DgemAAC20 votes -
Provide an API for querying deployment info
Please provide an API for querying deployment info such as friendly names, components, deployment notes, etc...
8 votes -
Add an auto-save feature while building deployment packages
As Gearset is run through a web browser, if the browser happens to freeze while a package is being built, you don't have the opportunity to save it as a Draft Deployment. An auto-save feature would allow someone to pick up where they left off, or when the last auto-save was done, without having to start from scratch.
45 votes -
download the zip package at an earlier stage before analysis has taken place
Download the zip package at an earlier stage before the analysis has taken place.
In big Orgs with multiple teams working the analysis page takes sometimes to load so it would be a great addition if we can download the zip package file and modify it.1 vote -
Avoid going to Setup | Deployment status on "validate deployment don't run any tests"
If you are deploying to PROD and
a) You have Apex classes in your deployment
b) You choose Validate Deployment - Don't run any testsThe Validation will fail and Gearset will tell you to check the target org Setup | Deployment Status where as suggested, the most likely cause is test coverage failures.
This is in fact true but it seems that Gearset could warn you before acting on a PROD deployment with non-test apex classes and 'don't run any tests' that this will be guaranteed to occur and give you a chance to reconsider your choice before wasting…
1 vote -
Access to Critical Updates
We use Gearset as our primary utility for managing various client orgs include Production and Sandboxes for Testing and Release Management. It would be great if there was also a way to access, review and potentially enable/disable any Critical Updates in any org from Gearset.
However, I do understand that Critical Updates may not currently be accessible from the metadata API.
Just a thought,
Mike1 vote -
Provide a way to deploy push topics
We have a push topic that we use but there is currently no easy way to deploy changes between orgs. Would it be possible to do this via Gearset?
1 vote -
Option to validate / deploy only running test classes in deployment set
When deploying, there's a pain point when we want to specify tests to run. It would be nice to have an option to only run test classes that are included in the deployment. Automatically identifying which test classes are in the deployment package should be fairly straight forward:
grep -ri @IsTest ./src/classes9 votes -
Show status in Chrome tab title
In Chrome, it is possible to display info even when viewing a different tab.
For example, I see this done with financial sites when they want to show the value of a stock ticker symbol.
2 votes -
Check for conflicts on CI
We have a scenario where CI would be useful, but there is a risk of it making destructive changes...
Orgs in involved are Prod, UAT, Dev.
Ideal development path would be Dev->UAT->Prod with each deployment using Gearset.
In the real world, admins make some changes directly in Prod. So, we also need to merge changes back from Prod->UAT to make sure that UAT is a realistic test environment.
It would be great if we could make a CI connection from Prod->UAT which automatically deploys non-destructive changes, and notifies us if a change cannot be sent to UAT for risk of…
2 votes -
Allow deployment of PROFILE only
The main reason we considered Gearset was issues with deploying profiles. Half the object settings, if not more, don't come over with change sets. When attempting to use Gearset to ONLY deploy a profile, we had the same issue. So, what's the point of using GS then? When I talked with one of your technical resources he did mention that was not a common use case. I would think it would be for large organizations like ours (over 3500 employees). We may want to spin up a new profile and just deploy that with no app or any other features…
10 votes -
2 votes
-
Filtering by user across the app
Filter deployment history & automated jobs to only show a specific team member's activity (e.g. mine). With large teams, the history pages can get too busy and makes it difficult to find the results I'm interested in.
1 vote -
Rollback deployments made by CI jobs
Manual deployments and change monitoring jobs can be rolled back. Add the same function to CI jobs in case it accidentally deploys something unwanted
28 votes -
Cancel deployment in progress
In Salesforce, you can cancel a deployment in progress: Maybe because a test has failed already and you don't want to bother running the rest, or because you forgot some things.
Can we have a cancel button while a deployment is in progress in Gearset? The metadata api seems to support it:
https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_canceldeploy.htm
9 votes
- Don't see your idea?