Matthew
My feedback
4 results found
-
2 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
An error occurred while saving the comment -
3 votes
An error occurred while saving the comment Would love this! There are some things that are definitionally different, so even comparing a fresh sandbox to production using the Default Comparison will result in a long list of diffs. These are mostly metadata-type Settings, SAML SSO configs, ContentAsset-related stuff (for orgs that use custom logos), plus lots of stuff related to LightningInstrumentation.
These meaningless diffs make it hard to see the stuff I care about, and it has taken me a long time to think through what I should exclude from the Default comparison and how (thanks Carly for helping me out with some of the LightningInstrumentation suppressions!)
The TL;DR is, if I do a comparison between a fresh sandbox and production, there should be no diffs, even though there may technically be things that are different. I would love a one-click way to hide those things that are different-by-default, (or better yet, Gearset could hide those by default and give me a button that says something like "show me everything" so I can more easily see the meaningful / intentional / human-created changes.
Or, perhaps you could create a different/supplementary status for those pieces of metadata, other than New, Changed, or Deleted, called Environment Specific (or something catchier!), so it's clear that there's a diff, but also clear that we don't expect that piece of metadata to be identical, so we can probably safely ignore it.
-
5 votes
-
1 vote
our team loves Linear and it would be fantastic to have it work automatically with Gearset!