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.
1244 results found
-
Allow
Once the comparison is completed. Gearset should tell us which commit Id belongs that changes.
Gearset should allow the users to deploy per branch. User will be allowed to cherry pick commit Ids then that commit ids will be package and able to deploy it.
1 vote -
Monitoring enhancement: compare permissions across users
It would be cool if the Gearset Permissions Explorer would help you in determining how to collapse Profiles into fewer numbers. The model would be https://perm-comparator.herokuapp.com/
A typical org has proliferated Profiles over the years, many only slightly different from one another. As SFDC wants us to move to Permission Sets, job one is to collapse the profiles into as few as possible - this requires comparing user permissions against each other (you can't just compare profiles, you need to know what additional permissions some users have vs others too)
Since SFDC is finally making dynamic Lightning pages GA (for…
1 vote -
Deploying to an org based on tags
It would be a useful feature to initiate a deployment when a Github tag is created.
1 vote -
Don't Delete Managed Package's object permissions from Permission Sets in CI jobs
In a CI job, using source control as the source and including deleted items, you can run into an issue where objects from managed packages show as "deleted" in terms of custom object permissions from permission sets that have access to them. This can occur for permission sets designed to give access to managed package features or if you have a permission set with "View all data" or a system permission that gives them access to all objects in some capacity (read, write).
Ideally, we wouldn't have to include managed package object permissions into Source Control (likewise, Gearset suggests only…
1 vote -
Avoid spurious differences in LeadConvert
SFDC seems to retrieve the lead convert settings in non-deterministic order between orgs . Display only true changes/adds/deletes rather than differences in ordering of the mappings as they make no difference to the runtime execution of Lead Conversion
1 vote -
it would be great if deployments could be done automatically based on a event trigger
To facilitate Automated Testing, it would be great if a deployment could be triggered by an event (such as a commit by a dev), so that an org is created to allow functional automated tests (not unit tests) to be run automatically without requiring any manual process
1 vote -
Provide the option to skip code coverage when running tests on a schedule
skipping code coverage on apex test execution, helps tests finish faster.
1 vote -
Avoid manual selection of component while compare and deploy
Good to have options in Gearset to auto select changed metadata files(changed as a part of pull request) while doing Compare and deploy.
Imagine one pull request number 5377 (which is changing 200 metadata files moved from 1 branch to another branch).
Now while doing compare and deploy It is good to have options which auto select this 200 metadata for comparison. This can help me from this manual selection of 200 metadata files which is very time consuming.1 vote -
allow users to customize Slack notifications
It would be great to have some ability to customize the notifications, specifically:
- change sender/title. right now it just shows up as my name.
- add a link to the monitoring history to allow wasy one-click into monitoring reports to see what specifically has changed.1 vote -
export deleted data records in CSV format
We can currently view deleted/removed data records in XML format as a list, but we can't export them into a CSV. This is necessary people who don't have access to Gearset and would be very helpful for users who have difficulty understanding XML.
4 votes -
Allow custom manipulations to data during a data deployment
Export the selected data source in a CSV file before deploying, in order to allow custom manipulation. Then allow the import of that CSV to destination - functioning like a more sophisticated Data loader.
3 votes -
Keep the same record owner between source and destination orgs.
Alternatively, allow the change of record owner before importing data to destination org.
1 vote -
add files to a gitignore during Suggested Fixes
When I make a comparison, Gearset will helpfully check the deployment and offer suggestioned fixes, such as... exclude object components belong to managed packages. now, i can agree to that solution and exclude those files, the problem is they persist every time i make a comparison, they always show up as changes. Would it make sense to be able to add them to a list of ignored changes?
1 vote -
Combine validated packages
Hi Team,
Please add checkbox for validated package as same as deployed ones. that way I can combine package even for validated one's and deploy.
10 votes -
Ability to merge the pull request from inside gearset. It gives me option to stay in one tool and carry out all my opertions.
In Gearset we have option to raise the pull request but we cant approve merge them inside gearset. There should be a checkbox which if checked should go and merge that pull request. That will allow the user to stay in one screen/one tool i.e. gearset. If someone wants to keep its approval processes in bitbucket then checkbox will allow them to only raise pull request and not auto merge/approve.
4 votes -
Exclude the subcomponents of the parent Workflow metadata and also exclude list views from custom objects
I want to exclude outbound messages from workflows as we will have different urls in different sandboxes. Same with list views we want to exclude them from custom objects so that we can use CI using gearset for deployments
1 vote -
Option to choose CI validation run behavior with Open Pull Requests and Branch updates
Currently, if you have a CI job set up to validate based on events (push, pull request) on a specific branch the following occurs:
You open a pull request against the specific branch noted in the job - CI validation runs
You push a commit to the source branch of the same open PR - CI validation runs
You push a commit to the target branch of the same open PR - no validation runsIn the conversation with Dan on 8/13/2020, I was told this is by design on Gearset's end (to ignore that situation) to avoid long queued…
1 vote -
Show associated JIRA ticket in Validated Packages & Deployment History and Export
We would like to view the associated JIRA in both the Validated Packages and Deployed History pages. In addition, we would like to export the associated JIRA tickets in the Export History Excel report, found in the Deployment History page.
We link our Jira stories to our Production deployments and we would need a way to report on which ticket is linked to which deployment. Currently this is only available if users are diligent enough to also write the story number in the Friendly Name or Notes.
This would be an extremely useful feature especially for companies undergoing SOX Compliance…
3 votes -
Only show JIRA tickets with specific statuses
We would like to the ability to only display JIRA tickets with specific statuses (e.g. Approved, In Progress).
1 vote -
OAuth support for outgoing webhooks
Currently outgoing webhooks support only basic authentication. It'd be useful to have oAuth support for outgoing webhooks for enhanced security.
5 votes
- Don't see your idea?