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.
194 results found
-
On Create Pull Request, auto populate details with commit messages
Similar to the way Bitbucket and GitHub work, it would be nice if the PR description was autopopulated from the commit messages (1 per line)
3 votes -
Customize CI job commit message
When a CI job pushes changes to source control, it always uses the message "CI deployment from job <CI job name>". It would be very helpful to be able to customize this message.
5 votes -
Revert with one click all changes from this PR
Please allow reverting PR from lower environments. In mine example, we had a feature that went through develop and uat and was waiting in the pipeline to be added to release but the business changed its mind and canceled this whole feature.
Please add an option that with one click we can revert PR and changes from lower environments.
Image:
https://www.dropbox.com/s/ohvymcs16p9n5ge/2022-06-30_14h10_44.png?dl=02 votes -
Include Deployment Name on Continuous integration dashboard
On the Continuous integration dashboard, specifically in the Validation only CI jobs section, there is no way to associate a validation job with the deployment dashboard in Salesforce. We have a validation only job set up to run tests on PRs when they're created. If we get a handful of them all at once, there is a long list of validation jobs running, but we can't tell which one is the one that's actively running. There is no link between the job in gearset and the job in salesforce.
3 votes -
to let us configure the default metadata filter by deployment pipeline configuration
Can we please have a possibility to configure the "standard" metadata filter by each deployment pipeline project?
I think it is currently preselected by the last used metadata filter from the standard comparison.
As we usually have a specific metadata filter configured by deployment pipeline project, it would be great that we can configure each project with a default one..
Thank you!
2 votes -
allow field level granularity in CI Jobs
Would like the possibly to set up a CI job that only syncs a sub-set of fields on a custom object. For example, we have an org to org sync where we want to update picklist fields but not autonumber fields. Currently we are running this job manually twice a day.
1 vote -
Possibility to validate a feature branch as a whole without having to select the Metadata type
It looks like the current validation jobs setup in Gearset needs the Metadata Type to be explicitly selected to perform the validation. This should ideally be optional and there should be a capability to just validate everything that is there in the feature branch against the target org. It's really annoying for us that we have to select the Metadata Types to be validated.
2 votes -
Clone Problem Analyzer Templates
With CI jobs, you may need to refine over time your Problem Analyzer templates
However, there is no clone button and you have to carefully set up the new template (as edit-in-place is not supported when the template is already assigned to a CI job - at least that is what the in-app guidance tells you)
So --
a) Allow Clone from page app.gearset.com/problem-analyzer-templates
b) Allow an easy way to assign the new template to all CI jobs without having to do each 1 x 12 votes -
Transfer ownership of an Org Monitoring job
Transfer ownership of an Org Monitoring job:
We are a consulting firm and a project team often changes during the life of a project. Right now if we have an org monitoring job tied to a project and the owner of that job is moved off the project we need to create a new job and perform a manual comparison.
It would be great if instead of all these manual step we could just change the owner of an Org Monitoring job.
4 votes -
Sort Validation Only CI Jobs
In the CI Job page, you can sort the top-level jobs by different columns (Job Name, Source, Target, etc...) but you can't sort the actual instances of that job.
We can get up to 30 PRs that are all being validated, and it would be nice to be able to sort them in some controllable way. It seems to rearrange them in whatever way it feels.1 vote -
Be Able to deploy Portal Sharing Settings and Organisation Wider Default Sharing Settings at the same time
For example if attempting to deploy
OWD permission Read -> Private, and Portal Sharing Set None -> Read. Gearset will fail validation due to SF complaining that Portal Sharing Settings cannot grant Read permission, since OWD is already giving that access.
Though what SF sees is that Portal Sharing Set is trying to give Read when it already has that access.Therefore, if I want to make the deployment then I would have to do in 2 steps.
1 vote -
Manually Delete Metadata after CI job runs
We don't want the CI job to delete metadata, so we've unchecked that box. However, when a CI job runs that would have deleted data, we'd like to be able to select from the job history, review what would have been deleted and elect to deploy the deletion manually post CI run. We can re-run the comparision from Compare and Deploy, but having this action tracked within the CI job history would be more convenient, and would allow the history for the target org to be contained in the same thread.
2 votes -
See when a commit validation was deployed or not (For CI validation Jobs)
When you go to the validation only CI jobs section within the Continues Integration part we usually have a CI job targeting a prod environment, you can see all validations succeeded and the commit attached to such validation, each CI job run contains 3 options:
View comparison
View Summary
DeployThen if the validation passed and the code indeed was merged from the feature branch to the master branch (Which would have triggered the actual CI job run), how would you be able to identify wether a merged pull request was deployed or not within gearset?
For me it's very…
1 vote -
Allow the creation of CI Jobs against Salesforce orgs that we are delegated to, instead of needing to be owner.
We have 2 admins that we want to be able to create all of the CI and Pipeline Jobs, even if they don't have their own credentials in a particular Salesforce org. They have Deployment delegation, and can run compare and deploys, but not set up integration jobs.
This is then requiring us to either, provision extra licenses in each sandbox for our DevOps administrator, or have the developers create the CI jobs, which they are not comfortable with.
And, as we start the Pipeline Pilot, we would like to leverage all of the existing CI jobs, but, that is…5 votes -
Additional text countries
I'd like to see a few extra countries added to the text messaging option on scheduled deployments. My team works with resources in different regions.
Brazil +55
India +91
Philippines +631 vote -
Allow Deployment Notes to be editable post-deployment
Allow Deployment Notes to be editable post-deployment. Our team uses very specific notes for auditing purposes, and being able to edit them post-deployment would make that process a lot easier for our teams.
3 votes -
CI Deployment on a Schedule
We would love to schedule a deployment from GitHub source to a few sandboxes at the end of each 2-week sprint.
2 votes -
Granular "difference types to deploy" on a metadata level
In the CI job, we would like to have the ability to specify on a metadata level if we want to deploy new items, update items and delete items. There are examples of metadata where we always want to delete and others where we don't want to.
2 votes -
Notification of unresolved CI job failure
As the owner of the CI job pipeline, I would like notifications when there are ongoing failures to the CI jobs that I select so that I do not have to continually monitor the jobs as a part of my day-to-day.
Acceptance criteria:
- The current-state suite of notifications on CI jobs will still be available.
- When a CI job has failed and the failure has not been cleared within X number of hours, the notification will be triggered.
- Each CI job should have blocker notifications enabled separately.
- Users will be able to select from SMS, email or both.
- Users will…
1 vote -
Add option to provide exact time in case automatic deployment
We need to set exact time for automatic deployment. We need this option for example for night releases for specific client. This is important for international clients that works in different time zones
2 votes
- Don't see your idea?