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.
1301 results found
-
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 -
Mask data that already exists in an environment
At the moment, we know that you can mask data whilst seeding it into an environment. However, what we would like a way to mask data that already exists in an environment.
A use case is that we have a full sandbox that contains customer data that we want to mask without needing to seed the data in first.
It's a common use case for organisations that deal with 3rd party suppliers but do not want their customer data exposed to the 3rd parties. For instance, a Salesforce implementation partner is delivering a project. They need access to the environments to build and…
3 votes -
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 -
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 -
Allow configuration of where pull request/merge updates are posted in Jira. User comments are being missed because of the volume of updates.
Allow configuration of where pull request/merge updates are posted in Jira. User comments are being missed because of the volume of updates from Gearset when moving a set of changes through the pipeline. These updates are important and we want to keep them, however having the ability of moving them to another tab/section on the Jira ticket would mean we could keep the comments section for user comments only.
2 votes -
Removing an Updates Sandbox from the pipeline should close all associated PRs and branches
I noticed that deleting a sandbox with outstanding updates from the pipeline does not close any associated PRs. These and their branches should be removed from source control automatically. The branches are especially problematic as the GUIDs make it extremely difficult to associate them to an environment and determine if they are no longer needed.
1 vote -
documentation
I have been really impressed by the visualizations on the Compare and Deploy interface. Particularly the lightning page layouts and flows. One of my most time consuming tasks is creating internal documentation and I have not found a tool that allows me to capture the level of detail that I want in an efficient way. It would be great if I could export the visualizations at the bottom of the compare and deploy screen. It would be even better if it could export directly to Confluence.
2 votes -
Add regex or other means to "exclude" strings in monitoring job
The Wave dashboards have a key field that changes every day and causes false positives in the Monitoring jobs. I would like the ability to exclude that string pattern from the results so I don't have a bunch of changes that don't matter showing up every day. Regex seems like the most robust way of defining it.
1 vote -
Allow configuring Unit Test jobs to run without code coverage
Ideally I would like to track code coverage, however due to an issue we're having with Salesforce, it's taking 12-24+ hours to run all local tests, crippling our ability to run unit tests nightly. I've discovered that when turning off code coverage when initiating test runs via the tooling API, test runs take significantly less time. We have been working with Salesforce support on this, but as a workaround it would be very useful for us to turn off code coverage for Unit Testing jobs.
2 votes -
CI jobs view improvements
Hi Team,
when opening a CI job and then expanding them, I can see a list of PRs with status 'Succeded' for two days I thought those were the successful deployments. Technical support confirmed instead that those are the PRs where the Validation Job has succeded but not yet deployed. The view is a bit confusing because for validation jobs I would expected a status = 'Passed'.
Also, when I open the 'View History' of the actual deployment job it takes me to a view where I can see the github ID but not the PR number/name. It would be…2 votes -
Offer Japan data residency
We are headquartered in Japan. Japan has data residency requirements for data backups/deployments and even metadata deployments/processing.
Please add the option for a Japan hosted Gearset account.
2 votes -
Quick deploy in pipelines
It would nice to be able to use the Quick Deploy feature once a release is validated, instead of either hitting deploy or scheduling the deploy and having it validate one again.
22 votes -
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.
2 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.
2 votes -
Allow out of order Update deployment
Currently you can only deselect and select update elements in an order. For example I have 3 recent updates ordered 1 to 3. One being the oldest and first update and 3 being the newest and last update. The current functionality would require me to select item 1 if I wanted to also update item 2. And if I wanted to update item 3 I would have to select all the items before it.
I would like to select each one individual no matter there deployment history. Often I need to do this because the updates have no relation to…
2 votes -
give a reminder if I'm leaving out a key piece from my deployment
When deploying a new field, not including any permissions would be strange so a reminder would be great. Think of it as a recipe. If I'm making a pastry and I don't include salt that would be odd so a reminder there would be needed. I might have high blood pressure so there's a reason I don't want to include it but a reminder is helpful. For some deployments its easier to make inferences than others but it's good to starts somewhere.
1 vote
- Don't see your idea?