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.
1456 results found
-
Add an option to not run the comparision part in CI job (sfdx like)
When you are pushing a project with sfdx, there is no compare, sfdx just push the whole package.
It will save a lot of times.
3 votes -
Ability to carry out action after successful deployment or detect org changes (monitoring)
After every release, we have to do smoke testing. We do have automated testing using selenium and we wanted to trigger the automated testing every after release is detected. It would be nice if in the deployment we can call an api or webservice after successful deployment. Or in the monitoring we can call an api when there's a change happened in the org.
2 votes -
Warn about Email Deliverability setting
Warn users when they are about to deploy (data OR metadata) to remind them when "Email Deliverability" is turned on.
1 vote -
Allow deployment of Email header/footer changes
Examine changes to Email Footers and allow deployment of changes.
1 vote -
Ability to chose SFDX source format (force-app) compare or old style (src)
Add a checkbox to chose wheter we want a sfdx compare or an old one (in order to not let gearset chose for us)
1 vote -
Jira Integration: Include the option to add a comment in JIRA with the URL of the pull request created from Gearset + Assign reviewers
After a deployment to a git branch, gearset allows to create the pull request from Gearset. It would be nice to:
1. Have an option to add the pull request URL to the deployment notes
2. Have the capability of add reviewers (users from the git repo) into the Pull Request5 votes -
Add Provar integration for testing to support companies that already have investment in Provar.
Integrate Provar for testing.
3 votes -
to add an option to not to run unit tests validation in CI job in case there are no changes detected
2 votes -
Manage multiple Gearset teams from a single Gearset account
I want to be able to manage multiple Gearset teams from a single Gearset account, and not have to log out and log in again.
18 votes -
Add a tab for Items that the Items I Selected Depend On
It would be so cool if there could be a tab that shows all the items that my selected items depend on. It would be much easier to review / select them then the way I do it now, which is expanding each item in the Selected Items tab to check for things I need to add.
Thanks!
5 votes -
Metadata filter - ability to select Report/Dashboard folders by parent folder name
When setting up a metadata filter for a new comparison, when it comes to Reports and Dashboards, it would save sooooo much time if they could be selected according to the top-level/parent folder that they reside in. That would enable the ability select all reports within a single parent folder at once, rather than having to select reports separately which reside in a nested/child folder.
3 votes -
Separate the Custom Settings <object> Permissions and Metadata Type permissions from the Profile or Permission set
When promoting Custom Objects and their security, we have to look at Custom Object Permissions (after loading the respective Profiles and Permission Sets in addition to the Custom Objects). We should follow a similar model for Custom Settings and Custom Metadata Types. The reason is that, if they remain part of the Profile or Permission Set, then I have to make sure that the Profile or Permission set exactly matches what I want in the target environment - I can't have any extra Custom Settings or Metadata Types that don't exist in the target environment yet or the promotion will…
1 vote -
Link to salesforce source records
When reviewing a Comparison with Salesforce as a source or target, include a link to the Setup/Configuration page that is being compared. For example, a link to a Page Layout that the user could click to jump right to the Layout in the appropriate Salesforce environment. There are times when we review Comparisions and need to see the source outside of Gearset and this gets the user there much faster.
The link would appear in the header of the Comparison window, near where "SOURCE" and "TARGET" are listed.
4 votes -
Account owner should be able to delete templates created by others
If a team member is removed from Gearset team, any template or previous activity can not be removed by anyone else. Leaving some clutter behind. It would be good to have the Owner of the Gearset account/team to have a super admin level access to all templates/data created by other team members so clean up could be managed....
2 votes -
Add Validate pull requests for custom git
We have self-Manged Gitlab as a git provider.
It would be good to have the possibility to allow to run validations on pull requests for custom git repositories orsupport on-prem GitLab (submitted as https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/39728857-add-validate-pull-requests-for-on-prem-gitlab)
7 votes -
add a wrning
when adding filters in the manage custom filters section can you a check to see if the contents look like regex, and the type selected is "object name" can you pop up a warning aong the lines of "Are you sure you don't want a regex filter?"
1 vote -
Options to pick only selected custom labels metadata for salesforce.
Since the custom labels metadata can’t be picked individually, the Gearset compare and validate process would pull in all custom label changes. This would be a concern if we want to withhold any particular custom labels from being pushed to higher environment.
6 votes -
Monthly sandbox refresh from production
I would like the ability to refresh a sandbox from production on a scheduled recurring basis on a monthly cycle (ex: from prod to a full sandbox) so as not to overwrite current development items that are in process or testing.
3 votes -
Support multiple SFDX projects for a custom GIT repo
When comparing / deploying using a custom git repository, containing multiple SFDX projects, present the user with the ability to select which SFDX project to compare / deploy, either by package.xml or sfdx-project.json. Currently Gearset fails and reports multiple sfdx-project.json were found.
[
{
"UserReadableError": "This repository has 2 sfdx-project.json files: Gearset cannot determine which one to use",
"ErrorType": "ErrorFromSource"
}
]2 votes -
Distinguish between process builder and flow
If you do deployments of flows and processes from process builder, both of them are handeled as a flow. If you need to activate the flow or process manually in a production org, you need to guess if it was a flow that you have deployed or a process.
Please within the deployment report (and the comparism), distinguish between flows and processes.2 votes
- Don't see your idea?