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
-
Create user friendly Audit API query process
The current process for finding deployments that included a specific component requires multiple steps including downloading JSON and working in a spreadsheet. It would be nice to have a UI that allows us to select a time frame and specific component API name and get a filtered list of deployment jobs within the given timeframe that included the given component.
1 vote -
Allow to export the data of an object or multiple objects for a specified time period
Through the UI or through an API allow to specify the Object (it can be the API name of it) and a time period e.g. 01/01/2024 to 31/12/2024 and generate an export of all records for that object in a zip with independent CSVs with all the data of that Object.
1 vote -
Save Problem Analyzer Changes to Deployment Set
When using the Problem Analyzer to identify and fix issues within deployment sets, it's common to add or remove items to address specific problems. Currently, these changes are not automatically saved, which can lead to recurring issues in subsequent analyses.
Suggested Enhancement:
Introduce an option that allows users to save their modifications directly to the existing deployment set or create a copy of the set with these changes. This feature would streamline the problem-solving process and ensure that resolved issues do not reappear in future analyses.Benefits:
Efficiency: Reduce the time spent on re-analyzing and re-fixing recurring issues.
Consistency: Ensure…5 votes -
Integrate with Continue https://docs.continue.dev/
My org already pays for Continue as an alternate to GitLab Co-Pilot
1 vote -
custom meta data filtering based on its value
Currently Custom Meta data records cannot be filtered based on what value they hold. This is a critical item, as we have several custom meta datatype record that would require to be filtered based on the value of a particular field in the record.
1 vote -
Option to create a CI job only for back propagation
We created some CI jobs for back propagation of changes from Production to other downstream branches and orgs. But these CI jobs also pick up pull requests(from a different pipeline) for forward propagation.
So, basically there is no way currently to create a CI job just for back propagation. It will be good to have a toggle in the CI job to mark it for forward or backward propagation9 votes -
Check for maximum flow versions reached as part of the pre deployment error check
The problem analysis does not detect that the deployment will fail due to max number of flow versions
2 votes -
Automatic sandbox updates option
The new sandbox updates process is really convenient - you can see all the updates a sandbox needs and apply one or more. However it is still very much a manual process to start it. We have a team of engineers and each one of them has to constantly go and trigger the update process manually whenever an update becomes available.
It would be really nice if there was a switch for 'Automatic updates' i.e. whenever it is turned on, the updates are applied automatically during off hours.
Of course if an update fails the engineer would receive an email…
3 votesThis is currently planned for later this quarter and next.
Users will have the option to:
- Bulk update selected dev sandboxes
- Automate developer sandbox updates; they will be immediately tried as and when ready
If users want to automate dev sandbox sychronization now, they can use CI jobs to deploy changes from their desired source of truth - this comes with some risk of affecting work in progress though.
-
Share a deployment with a different team
If I use my Gearset instance to deploy for a client, I wanted to share the deployment history visibility with the client's Gearset team.
1 vote -
Allow for CSV to be extracted data type from completed deployment screen
Allow for CSV to be extracted data type from the completed deployment screen
1 vote -
Assigning a dev sandbox to a member should give them deployment access
Assigning a dev sandbox to a member should give them deployment access automatically, or at the very least I should be able to give deployment access in the same interface.
3 votes -
Mass resolve auto resolved conflicts
Currently we have the auto resolve from previous environment feature which takes previous conflict resolution into account for a new conflict dectection run in a new environment. This is great but if I am deploying through a pipeline to multiple ORGs and the same conflicts that are auto resolved each time popup I need to keep clicking through them and marking as resolved.
I would like there to be a Mass resolve button that only resolves all the auto resolved conflicts. That way I dont have to click through each one even though everything is resolved already.
3 votes -
ability to clone the 'Deployment Pipeline' and edit the connections as per new project requirement
Every time a new project is kicked off , we need to setup the same pipeline with different org and bitbucket connection, gearset should have ability to clone the complete deployment pipeline so that only connections or branches needs to be updated for quick setup. Also some time the owner of the Deployment pipeline needs to be changed so this feature will give ability to clone the pipeline and disable the old pipeline.
1 vote -
Allow configurable default settings for Jira integration
Allow us to customize the default behavior for the Gearset<>Jira integration. Currently, Gearset posts a comment on the linked Jira ticket every time a commit is started and completed. This creates a lot of noise on the ticket.
Currently the only way to customize the messages posted to Jira are on a ticket-by-ticket basis. Allowing an option to customize this at the org/pipeline level (e.g. only post a comment when a deployment succeeds) would be very helpful.
3 votes -
View Locations Not Covered from test results
In the Salesforce's deployment result metadata there is details -> runTestResult -> failures -> code coverage -> Apex Class Name -> locationsNotCovered.
It would be very useful to be able to see the locations not covered of any apex class in the test results section of the UI.1 vote -
Re-introduce last used comparison filter
When I start a comparison, it used to default the filter to the most recently used filter. But now it always shows as "On-Demand Comparison". Can you please restore the previous feature...it's easy to overlook that the correct filter isn't shown and you can waste time doing a comparison against the wrong filter. Adam from your team confirms "Yea that was introduced when we overhauled our comparison tool, you'll need to switch to the filter you want to use each time."
1 vote -
precision deployment for Record types
precision deployment for Record types is required. currently when i try to deploy a record type gearset automatically adds all the picklist fields in that object. if we wanted to deploy only record type or only selected picklist fields currently its not possible. hence, precision deployment is needed for deploying record types
2 votes -
Fix Report/Dashboard Compares to honor RegEx "Include" on folder names (don't return ALL report folders)
Currently, if using regex to include only certain patterns for reports and dashboards, the regex works properly for the reports and dashboards returned, however, it has NO effect on the folder names. The Compare should ONLY return the folder names that match the same regex expressions if there are only include regex'es - it should remove folder names that do not exist in the regex expressions.
1 vote -
Allow Adjusted Column Sizes to Persist in the Comparison Table
Have adjusted column sizes persist once they've been adjusted in the comparison table instead of resetting with each selection. Deploying changes to permission sets could be dramatically streamlined if it's possible to maintain resized columns. If column sizes were set to accommodate the name instead of giving them all the same size, that would also be a huge improvement. The other columns don't include as much info as the name column so it's a waste to give them so much space. It is also inconvenient to caret down in permission sets especially when looking for multiple fields in one permission…
2 votes -
Add a Button to Retry Validation on Updates
The new Updates feature is great, but there isn't a "retry" button when there are validation errors to resolve. It's not very intuitive to have to cancel the update and go start over to retry after fixing validation errors. Currently it just shows that the validation failed and the update can be cancelled. It isn't clear what to do after resolving the validation error, and a retry validation button would simplify the process.
I had an error related to a manual change that needed to be enabled in my sandbox, and I had to cancel the update to get it…2 votes
- Don't see your idea?