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.
1444 results found
-
Include DataWeaveResource in comparisons and deployments
DataWeaveResource has been around for a few releases and is deployable via the Metadata API, but is not supported by Gearset yet. Please include this.
1 vote -
Persist Selection to Include/Exclude Managed Packages in Compare 2.0
When using the new compare, the default is to exclude managed packages. However, we'd like to always include them, so it would be nice to persist the selection from one compare to the next.
1 vote -
Adding Identity Settings to Metadata Deployment
Would be nice, if the Identity Settings can be deployed. Currently, every change on any Identity Settings page has to be done manually in each org.
1 vote -
Allow us to update the Associated Azure DevOps work item on a successful deployment
Currently within the successful deployment page, you can edit the 'Deployment friendly name' and 'Deployment Notes' which is a very handy feature.
However sometimes we would need to also update the associated work item as the wrong one can be mistakenly associated, this would be a very useful feature for us as a way of correcting such mistakes (that are in fairness rare).
1 vote -
Delta comparison between two unit test reports
Hi team. Would be good to have a feature that allows us the comparison between two unit test results. We are interested to export the delta errors from one day to another.
Use case: We are executing deployments for more than 50 pull requests against the same target sandbox, hence regression errors might be introduced throughout the day. We are running nightly unit test jobs and usually, in the morning, we have extra tests which are failing comparing with the previous day.
We are currently exporting the gearset errors from 2 reports, in Excel tables, and compare these ones to…
2 votes -
add Dashboard owner to Problem Analysis to use user deploying instead in xml ref
Spring '24 Salesforce added ability to change Owner on a Dashboard https://help.salesforce.com/s/articleView?id=release-notes.rn_rd_dashboards_change_owner.htm&release=248&type=5
"Previously, you had to clone or re-create the dashboard to provide access to a new owner."
This can now cause deployment errors when the Owner is changing between environments if the Uesr does not exist, similar to runningUser user references. Problem Analysis accounts for the latter, but not the Owner. Could we add the Owner scenario to this analysis rule?
1 vote -
apex classes dependencies
When deploying an apex class, check for dependencies. Currently it attempts to deploy even if there are missing fields and only reports missing fields one at a time. Very tedious to address.
1 vote -
Allow disabling of "Caching metadata for faster analysis"
Often this stage of the process seems to take much longer (upwards of an hour) than retreiving and analysing did in the first place.
It's unclear where this is even being cached, i've been told its in my own browser but this cant be true for a CI job with no browser available.
1 vote -
To have an option to run unit tests either for Validation or Deployment or both
Hi - for larger projects with 100 plus or more unit tests, deployments do slow down if there are a lot of them during the day and unit tests run twice. Once during validation and once during deployments. Can we have an option where unit tests can be turned on/off for validation and deployment separately?
1 vote -
Highlight "Failed Validation" Components
If the metadata Deployment Validation step fails, and the user clicks the "Back to Comparison" button, the components that caused the failure should be highlighted on the screen for manual review.
Currently, when a deployment fails on the validation step, my process is:
- Wait until the Validation step is done
- Sort by the Status to show Failures on top
- Take a screenshot of the list of errors (hopefully less than a full screen of errors)
- Click the "Back to Comparison" button
- Use the screenshot like a checklist to work through the errors
- Run Validation…1 vote -
Include the ability to tag/mention someone in the Gearset notes when linking a work item to Azure Devops
Currently, you can post notes in Gearset and these show up in the comments of any linked work item in Azure DevOps, which is brilliant!
The only issue is we cannot leverage the mention/tag functionality, including this would further streamline our deployment process and remove a manual step of having to deploy via Gearset and then manually tag a colleague to update them.
1 vote -
Roll back feature branches all at once
The tool works really well in the UI promoting things forward through the pipeline. You can select one or more feature branches and promote them one at a time or all at once. It would be great if you could do the same thing with roll-backs. This would make things clean simple and alleviate the fear that you accidentally left something out or accidentally roll-back something you didn't mean to
given that the need for roll-back functionality is inherently somewhat urgent, the tedious nature of having to carefully pick through a larger subset of metadata items to roll-back makes it…
1 vote -
Show Created by and Created Date in Comparison view
I'd like to see created by and created date in the comparison view. Sometimes we have multiple users working on items and I may not be the last to modify something but I am the one to deploy it and if I am the creator, I know what it is named but it makes it hard to sift down if I can only show modified by and modified date.
2 votes -
Bulk resolving merge conflicts across multiple PRs (set resolution as Feature or Environment)
It would be great if there was the capability to bulk-apply Feature or Environment when resolving merge conflicts across multiple PRs. I have a few dozens that all need to be set to the same option, and it would be useful to handle this quickly rather than click on each one individually.
3 votes -
Slack notifications for non-CI deployments
We use slack for monitoring which is great. We'd like to have the ability to setup more slack notifications for non-CI jobs.
Additionally, we'd love to see deployment starting notifications as an option as well, to allow our greater insights into when it's coming.
4 votes -
Expand integration for our Pipelines to allow us to enable tools like SonarQube and Veracode to run as part of our DevOps process.
We use tools like SonarQube and Veracode within our company to improve our security and code quality. It would be extremely helpful to have integrations with these tools or an open integration we could configure to work with them. Especially if that could be triggered as part of our pipeline process so this interaction is automated.
1 vote -
Improve Github Authentication and Access Control
While authenticating with Github, GearSet asks for too many access request including read/write access to all public & private repos which doesn't make sense.
Alternate Custom Git Auth does not allow teams to create team wide CI jobs.
And with User - specific CI Jobs, It does not allow us to setup "Validate open PR" jobs.Please provide better resolutions on authentication and job setup processes.
1 vote -
Invoke Run Anonymous Apex against target in CI Job
Team,
Can you please add Run Anonymous Apex option in a CI Job ?Step#1
In this scenario from Developer's end they should add pre scripts in a.txt file and add post scripts in b.txt file in their Source ControlStep#2
How it should work
- It should allow the CI job to run Pre and Post Deployment scripts
- Pre Deployment scripts should be picked up from Source control a.txt file and Post
Deployment scripts should be picked up from Source control b.txt file
- Post commit the diff of commit should identify what are pre and post scripts…8 votes -
Add to Problem Analysis option to auto remove DelegatedAccount tab settings
Add to Problem Analysis option to auto remove DelegatedAccount tab settings since it's an invalid tab and can cause validation/deployment errors. This saves a step of having to change Custom Object filter to Named Items and manually exclude DelegatedAccount when moving new profiles.
1 vote -
Option to not run job periodically
In the "Run job" field allow an option to don't run job periodically at all. Sometimes we nedd a job to run only manually, when needed, and now I need to remember to disable it manually each time
1 vote
- Don't see your idea?