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.
1382 results found
-
AI-generated PR descriptions are availble only while creating PR and these descriptions are not currently present in the Pipeline UI , Can
AI-generated PR descriptions are availble only while creating PR and these descriptions are not currently present in the Pipeline UI , Can someone please look into this and it's good if we bring that changes as well to the UI.
1 vote -
Can deployment bundles be created automatically based on JIRA labels or fields?
Can deployment bundles be created automatically based on JIRA labels or fields?
1 vote -
Allow teams to share and see progress in Launchpad
I've sent new team members the Launchpad site for training purposes. It would be great to be able to log in and see/track progresss.
1 vote -
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 -
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 -
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 -
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 -
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 -
Download multiple objects at once from a backup run
Given the related nature of many objects within a Salesforce Org. It would be helpful to be able to filter on and select records from multiple objects in a single data download.
1 vote -
Add the ability to track who configuration changes to pipeline, CI jobs, etc...
It would be nice to see when there's a configuration was changed such as required test configuration on a CI job or pipeline configurations.
1 vote -
Add a link to open the deployment when a change is being promoted
The pipeline view only shows that a deployment is "running" after promoting a change. It would be useful to have a link to the deployment job and be able to view the deployment status in gearset.
1 vote -
Mobile Support
Support mobile devices.
The CSS Used for the Pipeline Environment popover prevents the browser from scrolling horizontally. You can try this be logging into Gearset on your phone's browser or by narrowing the browser width on your desktop.
- I want to deploy from my phone.
- I want to monitor PRs from my phone.
- I want to browse my Scheduled Jobs and Monitoring Jobs.
1 vote -
Creating branch names from JIRA summaries can cause very long path names
Gearset automatically creates a branch name from JIRA summaries. Windows paths are limited to 260 characters.
error: cannot lock ref 'refs/remotes/origin/gs-pipeline/portal/SFBUS-33389/Update-Include-in-Export-formula-on-the-Intake-Criterio
n-object-to-prevent-Intake-Tasks-and-Intake-Document-Checklists-from-pulling-when-associated-to-a-process-that-is-not-included-in-
the-export-stage': Unable to create 'C:/Users/E19187/Repos/salesforce/.git/refs/remotes/origin/gs-pipeline/portal/SFBUS-33389/Update-Include-in-Export-formula-on-the-Intake-Criterion-object-to-prevent-Intake-Tasks-and-Intake-Document-Checklists-from-pulling-when-associated-to-a-process-that-is-not-included-in-the-export-stage.lock': Filename too long1 vote
- Don't see your idea?