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.
181 results found
-
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
1 vote -
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.
4 votes -
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/classes
11 votes -
Provide an API for querying deployment info
Please provide an API for querying deployment info such as friendly names, components, deployment notes, etc...
9 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…
12 votes -
Deploying Profiles - Create, Update, Delete
I have noticed that in some scenarios, user profiles cannot be created, deleted or updated. In addition, some pieces such as user license cannot be updated due to the Salesforce architecture. To create a new profile with a specific license, we would have to clone an existing profile that has the correct license and then update the permissions accordingly. When deleting a profile, first we need to ensure that the profile is not associated with a user (it doesn't matter whether the user is active or inactive) and then the profile can be deleted. When updating a profile, based on…
14 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
12 votes -
Allow deployment of Sharing Rules by Rule not by Object
In change sets we can pick individual sharing rules to push (specific ones on an object). However through gearset we can only push the whole object.
13 votes -
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?
2 votes -
Provide a way to init a sandbox
It would be nice if there was a quick way of init'ing a new sandbox that matches either what was in source control or an existing sandbox.
Currently, I need to run a comparison between the existing source and the new sandbox and then I can try the deploy, but it would be nice if the compare step was not needed and I could simply say 'overwrite what is in the sandbox with what is in the specified source'
6 votes -
Specified Test Level Suggestion
Hello,
It would be very nice to be able to have a test classes suggestion when doing a deployment with "specified test level". The suggestion will ensure the package elements will be covered at least by 75% and so speed up the deployment.
1 vote -
Extend the ability to add and delete in a single deployment to all metadata types
We just came across an issue in which we were deploying an HTML email template that had been moved from one folder to another in the source environment.
When deploying, only the delete happened on the first deploy. I needed to do a second deploy to handle the addition.
While probably not a common case, it's certainly important as the initial deployment reports that the addition was successful.
1 vote -
Filter Notifications for Non-CI Deployments By Successful or Not
When I do a deployment that is not a CI deployment, it can send an email. But the email goes out regardless if the deployment is successful. I would like to be able to send the email ONLY if the deployment is successful.
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 -
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 -
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 -
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 -
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
- Don't see your idea?