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.
1354 results found
-
Better pre-selection of repos & branches
My reasoning for the need:
Every day when comparing, I have to choose one github repo out of 343 (46 of mine + 297 from an org I'm a part of). Yes I know I can type some characters and it will search the list of repos, but it's still unpractical. It sometimes looks like it remembers the choice, but I think it doesn't quite work after logout and I have to select the repo from the long list too often.The bare minimum that would bring me pleasure:
The last used repo I used for any comparison would always…4 votes -
Allow changing of public group membership via Gearset
Right now, the only way to edit a group's membership is via the API (users or groups only) or the UI (additionally allows roles, roles and internal subordinates, etc.). Please allow the editing of group membership of public groups.
4 votes -
Org Management/Oversight Dashboard
I would really benefit from a dashboard option. A single place where I could see my CI Job history, Unit Testing Jobs and Monitoring/Backup history for all/a subset of my orgs.
I am using Gearset more and more to manage the state of my org's metadata, so it would be nice to be able to see it all in one place.
4 votes -
Search for components within Profile should show results regardless of expansion of specific profiles
Use case on Difference Viewer:
search on `profilerecordtypevisibility' (or use metadata filter and check Profile: Record Type Visibility)
Results
Unless the difference viewer already has the Profile(s) expanded for their components, you get no resultsDesired behavior -- Search on components within Profile should show results; even if search takes longer
4 votes -
When pushing Workflow rules and associated actions, gearset mistakenly says target objects do not exist
When pushing work flow rules and associated actions, if you do a compare with only workflow, then gearset prompts an error indicating that the target objects do not exist in the destination and that the rules should be removed from the package for the deployment to be successful. In this case, it told me Account, Event and Opportunity do not exist in the target. Including other metadata from the referenced fields resolves the issue.
4 votes -
Restrict source orgs
For example, deployments to a production environment should only come from the master branch of our git repository
4 votes -
Display "Metadata comparison (custom) filter" used on "Comparison in progress" -screen
Hi! I just started to evaluate Gearset. Looking good. When I was staring at "Comparison in progress"-screen this came to my mind:
Sometimes it takes a bit longer than expected and I start to think: "OMG - What custom filter I used? - Probably I'm comparing everything - That's why it takes so long - Maybe I should cancel this job?".
It would be more reassuring if the Metadata comparison (custom) filter being used was also shown on that "Comparison in progress" screen.
4 votes -
FogBugz integration for Gearset
We'd LOVE a FogBugz integration for Gearset similar to the new Jira Integration.
https://docs.gearset.com/feature-walkthroughs/integrating-with-jira
4 votes -
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 -
Allow teams to share custom git repositories
It would be nice to be able to share custom git repositories with the entire team. At this time, each team member that does deployments needs to configure each custom git repo in Gearset. Besides requiring them to set it up, it also means I need to give each person the credentials.
4 votes -
Include a field's permission if the field is flagged as a missing dependent component
If a field is identified as missing from the deployment and the user agrees to include it, the corresponding field's permission should also be added.
4 votes -
Improve comparison performance
If there is one thing that is :-( about Gearset is that for moderate size orgs (a few thousand objects), the default 64 comparison takes too long.
You want to initiate a deployment from source to target and, for whatever reason, you want to make sure you didn't miss anything that needs to be deployed
So, to be safe, you initiate the 64 default comparison.
And you wait (downloading, comparison). This can take several minutes. You go on to other tasks and your zeal to get the deployment done went off onto other things as the comparison time is too…
4 votes -
Have a timer on the compare page to indicate how long the compare is taking
Sometimes a compare can take us 30-45 minutes depending on the complexity of the org. I would like to see a running timer on this page of how long the compare is taking. I don't expect it to say how long is left, just how long it has taken so far. This will help to highlight if any abnormalities are happening, ie. if it's taking a very long time and is only at the Downloading phase for example.
4 votes -
Support deleting comparison data
Having the comparison history is a great feature, but it would be very beneficial to be able to delete any data in the system, especially when working with a trial account. Part of testing could include working with test environments that you don't want to persist after going live. Also, peace of mind when ending the trial that your data has been removed.
4 votes -
Expand the user security model to restrict user compare / deployment access to defined comparison filters
Hi guys -
In many instances, we would like to restrict user access to certain compare / deploy metadata filters. In our case, it would be rare that all metadata changes are to be deployed and we would like to give our engineers access to only certain filters. This would reduce the risk that items that should not be deployed at a high level will not be deployed. In the current model, if a user has deploy access, they can deploy anything and everything. This is what we are looking to avoid.
Thanks in advance for your time!
Best,
Richard
4 votes -
Modify the email address for manual deployment notifications
Being able to modify the default email address for deployment notifications, as for automated jobs, would help keep the others in my team notified of any manual deployments we run.
4 votes -
Unselect all standard profiles & related permission
Often you want to deploy Admin profile and (x) custom profiles. Compare and deploy picks up hundreds of entries for standard profiles which are surplus to requirements. A single click way would be veryuseful.
4 votes -
Using GitHub Apps to Replace Service Account for Team Shared Connection
Problem Statement / Current Situation:
For enterprise security compliance, organizations are moving to a model where all third-party integrations must use pure application-based identities (like GitHub Apps) instead of user-based accounts.
Currently, Gearset's CI/CD jobs require a "Team Shared Connection," (https://docs.gearset.com/en/articles/8455568-team-shared-source-control-connections) which uses a combination of a GitHub App for authorization and a separate GitHub "service account" user for commit attribution. While this is a functional workaround, it still forces us to create, manage, and secure a user entity in GitHub. This goes against modern security principles that aim to eliminate the management of all user credentials, even…
3 votes -
Pick up test classes to run from the apex class
Add a variable in apex classes where we can specify which test classes to run.
Recently you added the ability to specify the test classes to run on a pull request, which is great!
I know <ApexClassName>Test are automatically picked up by GS, but would be great if we could specify with
@TestClasses('CaseTestSuite,LeadTestSuite') or similar in the actual Apex Class and Gearset would automatically pick it up and add those test classes to the pull requests .3 votes -
Make pre/post deployment steps conditional on developer sandboxes.
Pre/Post deployment notes can be set to pertains to various static environments but they always apply to sandboxes after a back deploy. This should be conditional-- most of the time I only set them applicable to prod and they aren't applicable to developer sandboxes.
3 votes
- Don't see your idea?