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.
1361 results found
-
Copy reviewers to the cloned promotion branch PR in Pipelines (Bitbucket)
When Pipelines creates a promotion branch and copies a PR that was opened in Bitbucket, it does not copy the reviewers. This means reviewers have no way in the Bitbucket UI to filter for PRs that they're assigned to review.
Further, since all the cloned PRs are authored by the Pipeline owner, the lack of reviewers on top of that makes it quite difficult to visually differentiate between the list of open PRs, especially if you're both someone who creates & reviews PRs.
3 votes -
Ability to Filter Out Namespaced Metadata
I figured the best way to write this out was in the form of some sub-par user stories.
As a Salesforce Admin, I need the ability to do a comparison of two orgs/repos and have it show only non-namespaced metadata so that I can easily distinguish between things I own and manage vs what are from managed packages.
As a salesforce Admin, I want to be able to indicate that I want to hide all namespaced metadata while still being able to show custom fields I create on a namespaced object so that I can quickly deploy new custom fields.
…
3 votes -
Allow all admin users to run the 'Take Snapshot' functionality on Monitor jobs not owned by them
I would like all of my 'Admin' users (or specify which users in my org) can have access to run monitoring jobs I've set up.
The scenario is that we're a small team, so I want to set up all of our monitoring jobs, but if an issue occurs while I'm OOO any of my other team members could run the 'Take Snapshot' function to determine which changes occurred since the last monitor job ran and roll the changes back.
Currently users can edit/delete monitor jobs of other users and if provided 'Deployment' access can roll the changes back, but…
3 votes -
Let the user post Jira comments as internal or customer-facing from deploys
When deploying from sandbox to sandbox, we'd like the comments to post on the tagged jira issues, but would like to keep those comments internal instead of updating our clients. It would be good to have a security selection option when posting comments from gearset to jira.
3 votes -
Allow Record type additions and removals to be selectable
I am not a having an option to deploy the particular picklist values in the Record type level, I would like to include only the values I have added that are different from my target environment.
3 votes -
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 -
Notify GitHub that checks are running sooner
When a PR in GitHub is being validated, Gearset doesn't let GitHub know that the check is happening until after it has run the comparison between GitHub and the target org. Then the check is pending while the validation runs in Salesforce.
This means that there is a delay between when you create a PR and Gearset's check appearing as pending in the PR. At that moment, it looks like there are no more checks to run in GitHub so you can go ahead and merge. But, you really should wait until Gearset has compared and validated the changes.
It…
3 votes -
Delete GitHub webhook when the CI job is deleted
When we create a CI job where the source is GitHub, Gearset can automatically create a webhook for us in GitHub.
Would it be possible to delete that webhook in GitHub when we delete the CI job from Gearset? I've got some GitHub repos with failing webhooks due to CI jobs I once created. Obviously, I can tidy up manually from GitHub, but it would be nice to have the option of Gearset doing it for me. The URL seems to be unique to the CI job, so I can't see it having any negative consequences.
3 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 -
Make Gearset more responsive via web design
Currently when doing deployments I have realized when i migrate to a smaller screen that gearset isn't super responsive and sometimes i have to drag it back to my larger monitor. This was really highlighted when I was attempting to deploy some metadata from my phone (mac was updating).
Please make gearset more responsive so I can deploy from my phone.3 votes -
Require a Deployment Friendly name
Add option to require a Deployment Friendly name, similar to the current settings to require deployment notes and Jira tickets
3 votes -
Enable source control as source/target in Data Deployments
It would be great if we could add source control as an option for Data Deployments, this will be useful in cases where we want to backup copies of CPQ record data which manage configurations to our source control repository.
3 votes -
Have an ability to modify message which is posted to Slack channel.
It would be nice to have the ability to modify this notification message somehow.
E.g. include a number of PR which was merged into the main branch. Or remove extra information such number of deployed components.now it looks too big
Gearset Continuous Integration
A continuous integration run succeeded for ***** CI/CD. The job was a deployment.
Changed objects
3
New objects
0
Deleted objects
0
Source commit
1c***f2b3 votes -
Enforce each deployment to have a Jira issue in a specific status in order to be able to deploy.
As a gate-keep; to be able to deploy anything to production (or any other named environment), the associated Jira ticket must be in a pre-select status.
For example, the Jira ticket's status must be in "Ready for Deployment" to allow an end-user to deploy.
3 votes -
Support SAML-based SSO and SCIM-based user provisioning
To improve security, user experience and reduce user administration time, SAML-based SSO and SAML JIT provisioning or SCIM-based provisioning would be fantastic.
3 votes -
Ignore Business Owner changes between Sandboxes
This was marked as "Completed" in https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/39507649-resolve-data-owner-user-metadata-from-difference
But really the issue remains.
When "Business owner" is populated in a field, it will show as "different" since the XML is showing username, which is different between sandboxes.
This make trying to do comparisons to find differences very challenging.
3 votes -
comparison between 3 or more ORGs
i would like to see in a future update about comparing 3 or more Orgs to possibly fine tune checks between production, and multiple sandboxes to make sure everything looks as needed to verify no sandboxes are overlooked for refreshes if needed.
3 votes -
Automatic Validation of Pull request for AWS code commit
Gearset does not support PR validation for AWS code commit. We are cloud-native and use AWS extensively, thus missing out on most important feature of gearset. If you can support it it will be amazing and lifesaver for us.
https://gearset.com/blog/set-up-automatic-validations-of-pull-requests/
3 votes -
Allow retention policies to be set on individual core objects
It would be useful to be able to set individual retention policies on core objects, rather than on the entire backup job. This is for an old org (c.10 years), ideally you'd be able to set differing retention policies on different objects; e.g accounts after 7 years but contacts after 5 years.
3 votes -
provide the ability to add tags to branches within Azure DevOps.
Within Azure Devops you can group commits and changes into a release based on a tag. So for a user to be able to add that tag when they are associating a workitem to a commit would mean they didn't have to go into Azure Devops later to add the tag.
3 votes
- Don't see your idea?