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.
1308 results found
-
API to provision users, assign users to connected organisations
API to provision users, assign users to connected organisations
It would be hugely benificial to us (60+ connected organisations, 25 employees working in teams for multiple clients at a time) if we could programatically provision/deprovision users and provide access to connected organisations via an api.
At the moment this is error prone manual work that has to be done by someone with high level access (and as such is usually already short on time).
6 votes -
1 vote
-
call webhook with scheduled deployment
We would like Gearset to call a webhook when a scheduled deployment completes. The message to the webhook should pass a message with the org name, UTC datetime, the deployment friendly name, URL of Gearset deployment results and a status field with 'succeeded' or 'failed'
3 votes -
1 vote
-
Include Apex classes imported into LWC
Ensure that Apex Classes imported in LWC javascript files are included in dependencies.
2 votes -
`Deployment history' User Interface update.
In `Deployment history' it would be great if when you choose a target and it opens in a new window. Deploying 48 packages and it is painful.
1 vote -
Allow merging functionality when two branches are compared
right now, when compare/deploying two branches, Gearset only fetches the new changes and creates a whole new separate commit to be pushed to the targeted branch. This causes the targeted branch to lose track of all previous commits from the source branch and when compared in git, it thinks that the targeted branch is still behind. It would be very useful, especially for admins, to be able to use merge compatibility if and only there is no conflict between the two branches.
1 vote -
Ability to Compare metadata filters
When we have too many metadata filters, it is getting hard to keep track of them and figure out the similarities between them. It would be great to have an option to compare custom metadata filters.
2 votes -
Add a column to indicate if XML matches if order doesn't matter
See this link: https://docs.gearset.com/en/articles/2413367-why-is-xml-order-of-some-metadata-in-the-comparison-results-different
Sometimes, the XML of an item in sandbox/production can be the same, but not in the same order. This leads to false positives showing up in the list as "changed items".
I understand that sometimes order matters (eg: in picklists) but maybe there could be an additional column which shows if there are no differences if you ignore order? Maybe even a setting to turn the column on and off so it's not confusing?
1 vote -
Add 'run selected tests' in nightly scheduled Unit Tests Jobs.
We can select which tests run in Validation. It would be great if we could do the same in a nightly monitoring job.
2 votes -
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 -
Changed by and Changed Date not populating from DX structure in Repository
Using the DX/source structure in a repository (Github), no "item changed" date is shown for any metadata types in the comparison window.
This leads to gearset not being able to provide last changed date or who last changed anything in a Source DX repository. It's left with "unknown" and makes our comparisons and selections more difficult when users rely on that information.
1 vote -
Ability to override custom metadata field settings per org
Our code repository currently contains the custom metadata settings from our development environment. When we deploy to production, we either ignore custom metadata in Gearset and manually add any new custom metadata items to production or we manually select the new custom metadata items in Gearset and then manually update the fields in production from the development settings to the production settings.
It would be great if there was something like the Octopus Deployment tool has where you can define configuration settings for each environment. Gearset would automatically update the field value based on the stored setting for the specific…
1 vote -
facilitate selection at the UI of related permissions for selected items during deployment
Our typical use case surrounding related permissions for selected components (application visibilities, class accesses, field permissions, layout assignments, object permissions, page accesses, record type visibilities, tab visibilities) is to need to ensure that if a component is selected, its related permission is always selected also, with respect to a target set of profiles. We suggest you provide an affordance at the UI that selects related permissions en masse rather than requiring individual mouse clicks for each permission selection as at present.
2 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 -
Modify the "Changed On" drop down filter groupings to round to the nearest day, rather than the exact time the change was made.
It would be helpful if in the "Changed On" dropdwn filter if it grouped it into days, rather than the exact time the change was made. Also, if there were preset groupings like "Today","Yesterday","Last 7 Days", etc.
5 votes -
Provide integration with WebexTeams
We moved from Slack to WebexTeams and have lost the ability to post deployment notifications from Gearset. Here's an article about Webex Bots: https://developer.webex.com/docs/bots.
3 votes -
create a compare/deploy function for data similar to metadata
having something like new/different/deleted for data (so we can compare, say, products vs new product options or features) like we do for metadata
5 votes -
Export test run history
Exporting the Test run history to Excel/CSV will allow keeping trends.
The ultimate goal is to include this in a dashboards. If an embedable web page could be generated with solely the trends, that would be perfect.
2 votes
- Don't see your idea?