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.
1355 results found
-
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 -
The number of differences does not appear to the left of the Prev/Next buttons in XML view mode
However, the number of differences does appear when viewing the same Apex class in APEX view mode.
2 votes -
2 votes
-
Manage Orgs Re-authorization returns you to a default sorted list.
I refreshed a sandbox. I need to re-auth my orgs. I go to Manage Orgs, and sort by my friendly name. I click re-auth, and OAuth is successful and the app tells me I did a good job. But the page it returns me to is using a different sort then I left the page with. ie, it sorts the list by username again. Just extra button clicking I'd like to get rid of if possible. I have to re-auth orgs all the time.
2 votes -
User Account Specific Validation Errors
When deploying objects such as reports to a Target ORG, sometimes the reports are shared with a user in the source ORG. If the user does not exist in the Target ORG, the validation throws an error. Would it be feasible to add objects, such as reports, to the Warnings / Fixes screen so we can easily select how to handle user specific dependencies? Maybe we can chose to enter a new username or simply remove the shared with permission on the object?
2 votes -
Dependency Engine enhancement for Sharing Rules
Dependencies with sharing rules. Roles/Groups/Fields referenced in sharing rules may be helpful to add as "dependent" on as if they are not in the destination org you cannot deploy.
2 votes -
Scroll to top of category, when switch between All Items, Changed Items etc
Just a user preference item – when you switch tabs (ex: New Objects to Deleted Objects), it doesn’t place you at the top of the window.
So if I scroll down through all the New Objects and then switch tabs to the Deleted Objects, it just places me in the same relative location as I was in the New Objects tab.
It would be nice to have it reset to the top of each window when I switch tabs.
2 votes -
When migrating ReportFolders, either remove running user or let me map users between Sandboxes/environments
When migrating ReportFolders, either remove running user or let me map users between Sandboxes/environments
The SharedTo User doesn't exist in the target org causing my deployment to fail.
2 votes -
Creating branch names from JIRA summaries can cause very long path names
Gearset automatically creates a branch name from JIRA summaries. Windows paths are limited to 260 characters.
error: cannot lock ref 'refs/remotes/origin/gs-pipeline/portal/SFBUS-33389/Update-Include-in-Export-formula-on-the-Intake-Criterio
n-object-to-prevent-Intake-Tasks-and-Intake-Document-Checklists-from-pulling-when-associated-to-a-process-that-is-not-included-in-
the-export-stage': Unable to create 'C:/Users/E19187/Repos/salesforce/.git/refs/remotes/origin/gs-pipeline/portal/SFBUS-33389/Update-Include-in-Export-formula-on-the-Intake-Criterion-object-to-prevent-Intake-Tasks-and-Intake-Document-Checklists-from-pulling-when-associated-to-a-process-that-is-not-included-in-the-export-stage.lock': Filename too long1 vote -
Add a notes field to environment variables to contain the scenarios it's addressing.
For example, the RegEx allows finding of many different patterns that can all be handled by a single regular expression. Down the road it's less obvious which situations the regex was intended for. Having a simple notes field could be quite helpful.
1 vote -
Add a notes field to environment variables to contain the scenarios it's addressing.
For example, the RegEx allows finding of many different patterns that can all be handled by a single regular expression. Down the road it's less obvious which situations the regex was intended for. Having a simple notes field could be quite helpful.
1 vote -
Restore feature branch when a mid-flight promotion branch is restored
Have just experienced a scenario where closing a PR that is mid-flight in the pipeline caused the promotion branch and underlying feature branch to be deleted. So far, so good in terms of expected behaviour due to my pipeline settings. However, after restoring the promotion branch in order to reopen the PR and promote it in the pipeline, the next environment on the pipeline did not then show the change. This, I believe, was because restoring the promotion branch DID NOT restore the feature branch. Therefore there was no source to create a new promotion branch from in order to…
1 vote -
Create a mass back propagation button
Its very time consuming to have to back propagate one by one to each org. Please create a mass back propagation button.
Also when back propagating where more than one connection to an org exists for instance our techdebt org has several admin connections and I have to hit update on all of them. Make the back propagation smart enough to know that it only needs one update rather than on each connection to the same org
1 vote -
Feedback Search Bar
On the Feedback page place the Search bar at the top. Its odd that it sits at the bottom of the right panel
1 vote -
Grouping more than five sandboxes should not hide them
When grouping sandboxes, having more than 5 in a single group adds a scrollbar, and hides any additional sandboxes added to the group. This decreases visibility into sandbox status. I missed that there were several sandboxes that were very out of date simply because I couldn't see them on the pipeline. All sandboxes on the pipeline should be visible for visibility.
1 vote -
Please update your "Configure and deploy" option to allow the user to limit the records that will be masked in an object. We only want to m
Please update your "Configure and deploy" option to allow the user to limit the records that will be masked in an object. We only want to mask our homeowner records in Account and Contact. We do not want to mask our dealer records. If we could limit the records that are being masked by using record types, this would enable us to use your solution. Thanks!
1 vote -
Allow backup job permissions to be control by Roles
Backup permissions are separate from the Roles, causing duplicate permission maintenance. Please allow backups to use Roles instead
1 vote -
Pipeline Notification for Metadata filter for Missing components
If I am committing some code via pipeline, in my feature branch that includes a metadata not present in my current CI Job filter, Can I get notified from Gearset that commited/merged metadata not present in the CI Job Filter?
1 vote -
Ability to "Hide" Sandbox Groups on Pipeline Page
In the Pipelines page, it would be very helpful if we had the ability to "hide" entire sandbox groups from view. This would make it much easier to quickly find and focus on the environments that are relevant to the logged-in user.
Ideally, this "hidden group" setting would persist across logins and page refreshes, similar to how the "collapse group" feature currently works.
I'm sure an "unhide groups" feature will be needed with this as well, in case a previously hidden group becomes relevant again.
1 vote -
Allow Archive Notifications for both successful and failed runs
Currently, when an archiving policy runs, you can send out a notification if a run has been successful or a notification when a run has failed. I cannot see a way to have both notification types as I would like to see at a glance how many records have been archived in each run, but I also need to know when it fails with permission issues after deployments or major releases. I do not go into the Archive section every day.
1 vote
- Don't see your idea?