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
-
Include support to name space filter to include option to include unlocked packages with no namespace
Currently there is no way to retrieve and compare components belong in an unlocked package with no name space without using the 'include managed package' namespace filter 'all' option.
this might include too many items that I am not interested in.
4 votes -
Report Missing Dependencies on Lightning pages
Right now, if you include a lightning page in a deployment and do not include any of the components on the page (list view, report chart, etc), the problem analyzer finds no issue with it.
Even if the report is not in the target or is included in the compare, the analyzer always finds no issue with the lightning page.
It'd be great to have it function like other metadata where it would alert you to missing components in your package (by suggesting to include all referenced list views, reports, etc on the lightning page).
4 votes -
Allow Scheduling of Comparison and Export Results via Email
Our use case is to schedule the comparison of two sources (Salesforce orgs) which are both "dev" environments, on a daily basis, yet receive the comparison results as an email attachment. The format of the export file within the comparison itself is what we'd need. This would save time & clicks by not having to log into the app and dig into the comparison job to manually extract the csv file.
4 votes -
Categorize Meta Data Filters
Allow the custom meta data filters to be categorize or put in folders. You could organize your filters by customer, deployment type, etc..
4 votes -
Provide more detail in Monitoring notifications
Right now, the Monitoring job notifications (Slack especially) provide very little detail as to what actually changed.
Ideally, I'd be able to see right in the message (or in a threaded reply), the first X number of metadata changes made. If there are more than that, then providing a direct link to the detail page in Gearset would be great.
As of now, it simply just says "there were changes", with no detail or way to easily see the changes in Gearset...which is not terribly useful.
4 votes -
Permission sets not deploying correctly
When deploying a permission set, it was being deployed without the permissions checked, even though Gearset detects that the permission is checked in the metadata compare.
4 votes -
Selectively filter managed package metadata without excluding unpackaged components
Add the ability to filter in/out managed package elements from a comparison set at metadata type level. e.g. allow for the comparison of managed package objects and fields but exclude other managed package metadata types whilst allowing those types to be available for non-packaged constituents. More specifically for instance, exclude manage package page layouts and include managed package custom fields whilst including both unpackaged page layouts and custom fields in the comparison set.
The reason for this is to minimise the comparison set which can reach limits due to size whilst including all mandatory metadata elements for a deploy.
Using…
4 votes -
4 votes
-
Attach pdf items details in the email notif "Your organization has changed"
When you receive a notification concerning a change into an organization you need to know quickly which items are changed.
4 votes -
Stamp a validated package with the username of the person who clicked 'Validate'
Currently, a validated package is created by the owner of the draft deployment package, even if someone else was the one to actually press the 'Validate' button. I would like to have the username of the person who actually pressed validation to be noted somewhere in the validated package for auditing purposes.
This would help us be compliant with processes where we need a record of separation of responsibilites bewteen users.
4 votes -
include the Name/ID of the Deployment from Salesforce into the Deployment Report generated by Gearset
Include the name/id in the deployment detail page within Salesforce in the Gearset deployment report so we can trace and match those details to a deployment run in Gearset.
4 votes -
See Continuous Integration Deployments in the Deployment History tab
List deployments resulting from a CI job on the Deployment History tab along with manual deployments.
We currently deploy metadata using both manual and CI jobs and it would be convenient to see all deployments in the same list (for debugging, reporting, monitoring).
4 votes -
Show the latest commit(s) in the slack notification
It would be extremely useful for the development team to see the last set of commits which were deployed via an automated job, so that if it breaks it is easier to tell what broke the build or if it is successful what the org has been updated with.
4 votes -
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
- Don't see your idea?