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.
1377 results found
-
Enable the ability to use Capturing Groups as part of the replacement in Environment Variables when using Regex
Twice now we have run into issues with deployments that would be satisfied by having the ability to use the capturing groups of the Regex expression in the Environment Variable to populate parts of the replacement.
A good example of this is usernames in Assignment Rules. Salesforce exports the assignment rule metadata from a developer sandbox without the sandbox name on the end. So, in the metadata file it has user@domain.com instead of user@domain.com.sbx.
In criteria you can also be filtering on email addresses, so if you just look for @domain.com in the environment variable, it will also find…
1 vote -
Create Templates for Data Backups
During creation of Data Backups some requirement needs to be met across all jobs, so would be very good if we could replicate those requirements through a data back templae.
In my example I cannot backup files, attachments, documents, etc, so I need to create a job using the recommended selection, then edit the selection removing the objects I don`t want and replicate this same process across all the existing and new jobs.1 vote -
Show doesRequireRecordChangedToMeetCriteria on Flow Navigator
The doesRequireRecordChangedToMeetCriteria toggle on flow Decisions doesn't show on Flow Navigator, making it harder to check for issues on builds when using the comparison tool.
doesRequireRecordChangedToMeetCriteria should show in the flow navigator, same as the rest of the decision configuration.
2 votes -
Remove "No Difference" items when commenting on jira tickets
when i connect a jira ticket to a commit, I like the way gearset posts a comment on the jira ticket listing the changed items. what I dont like is the long list of "no difference" items posted on the ticket. It makes the ticket comments super long and annoying to scroll through. can gearset update this to only post the difference metadatas, or at least give us the option to include or exclude
10 votes -
Enable Excel export of org differences—profiles, permission sets, and objects—in the same side-by-side format with change indicators
I compared two profiles from different orgs—specifically, the old and new environments of the same company—to identify any differences and present them to the client for review and approval of necessary changes in the new org. However, I was unable to export the comparison results into Excel. It would be extremely helpful to have the ability to export the comparison data in the same structured and visual format as shown in the Gearset comparison window, making it easier to review and share with stakeholders.
2 votes -
Ability to link a existing PR to service now task or Incident
Currently Service now and gearset mapping only limited to Releases and Change Requests. In our company we use Requested Items, Request and Catalog Tasks, Incidents. We want Gearset PR Number to be linked Requested Item in Service Now .We want to display PR details on Requested Item in Service Now .
1 vote -
Provide a visual indicator on upstream systems when out of sync with master
Often times we see drift items added to PR's in our upstream systems. It would be nice to have an indicator that shows if a static branch is out of sync with master.
2 votes -
Automate upstream branch syncing
After merging/deploying to prod allow auto-creation of sync PR's to upstream branches/orgs (QA, UAT, Staging, etc...). If the sync PR's could be promoted automatically that would be amazing.
2 votes -
Add Pipeline Functionality to Handle Environment Refreshes and Branch Realignment
In many Salesforce development workflows, environments (especially static ones like UAT or SIT) are periodically refreshed from production. When this happens, the environment’s metadata and configuration can become out of sync with the branch linked in Gearset Pipelines.
This especially occurs when:
- Changes were made directly in production that didn’t flow through the pipeline, but now exist in the refreshed sandbox.
- A deployment was started partway through the pipeline but never completed to production, leaving partial changes held on branches in the repo.
Currently, the workaround is to manually run a comparison and commit the differences to realign the branch.…
1 vote -
Introduce precision deployment for Experience Sites.
We have multiple changes in train at any time across our three Orgs within our pipeline. We do not manage these changes via our pipeline due to some of the UI changes being made by Community Admins outside our Devops framework. At times we may have 3 separate features impacting a single page and we need to promote these changes separately. At the moment the Org to Org deployment takes the components in their entirety.
1 vote -
Add support for Jira Service Accounts
Jira has (finally) added Service Accounts, so that full Jira users are no longer required. Would be great to take advantage of this. For reference: https://support.atlassian.com/user-management/docs/understand-service-accounts/
1 vote -
Need to store the Source record ID from source to target org
When moving data from Org1 to Org2, The record ID from the source needs to be stamped in the target org in order to update that in the future, and this will be really helpful.
Thank you.
1 vote -
Change the test running options in pipelines
The options for tests in CI jobs/pipelines don't seem to offer quite what I need for sandbox deployments. Specifically, I want to be able to run all the tests when class/flow/trigger metadata is changing but no tests when tests metadata do not change.
This is possible to do when deploying to production orgs by using the "Salesforce default tests" option (see https://docs.gearset.com/en/articles/1376067-setting-apex-test-levels). But it is not possible in sandboxes.
In sandboxes, the "Salesforce default tests" option runs no tests at all which I don't want. I also don't want to run "All your tests" because if merging a branch…
1 vote -
Delete Flow by Version Number
It would be beneficial to delete specific inactive flow versions. Examples where this would help streamline deployment changes:
You need to delete a custom field that is used in a flow. You create a new version of a flow, remove the dependency on the custom field and activate the new flow. Now you want to remove the flow version that still has the custom field dependency. Something like a checkbox to select the version(s) to remove.
You have inactive versions of a flow and you want to clean up the historic flow versions. Something like a checkbox to select the…
2 votes -
Add folders to Data Deployments for better organization
To help with organizing data deployment templates it would be great to have some sort of folder structure to allow us to group data deployments by team. We have several Salesforce Teams at my company and we all have slightly different data deployment needs. It would be great to have team folders for data deployment templates...for example Sales Team Templates, Service Team Templates, Marketing Team Templates, etc. Today we use some naming conventions which is fine, but would be a little cleaner if we had a folder structure. Thanks for your consideration.
2 votes -
focus
When viewing a Comparisons results and click the filter icon in the column header to filter that column, it would be nice for the focus to be automatically placed on the filter text so it can be typed directly (without having to click on the filter text field).
1 vote -
checkbox
When viewing Open Pull Requests in an environment in a pipeline, the user can click the checkbox beside the pull request thinking they have selected that pull request. Clicking the checkbox does not currently select that Pull Request in the UI. It would be nice if clicking the checkbox would also select the current Pull Request in case another function such as "Close pull request" (trashcan icon on right pane) is being selected.
It is easy to think you have selected the pull request when clicking the checkbox for it and in turn close the wrong pull request as a…
1 vote -
svsvdv
Dbbdbdvdbfbdbdv
1 vote -
Enable AccountContactRelation standard object as part of data deploy
After chatting with support, it seems to be impossible to deploy an AccountContactRelation record when IsDirect = TRUE, meaning the AccountContactRelation is between a Contact and its primary Account.
When I try deploying an Account record, Contact record and the AccountContactRelation record that joins them as top-level objects in the same deployment, I receive the error "INVALIDCROSSREFERENCE_KEY:You can't associate a private contact with an account.:ContactId --", presumably because in the order of operations, the Contact hasn't been updated with the Account lookup yet.
When I try splitting this into 2 deploys, deploying the AccountContactRelation alone as part of…
1 vote -
I would like to suggest a feature for Gearset that provides a more granular control over user permissions. Specifically, it would be benefic
I would like to suggest a feature for Gearset that provides a more granular control over user permissions. Specifically, it would be beneficial to have the option to allow a user to commit changes to a branch but block their ability to create a pull request (PR). This would allow our team to review the commits before a PR is opened, providing a more effective way to manage and correct any potential issues before they impact the main repository. This is an improvement that would significantly streamline our workflow and reduce the risk of errors.
1 vote
- Don't see your idea?