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.
1413 results found
-
Jira Integration: Include the option to add a comment in JIRA with the URL of the pull request created from Gearset + Assign reviewers
After a deployment to a git branch, gearset allows to create the pull request from Gearset. It would be nice to:
1. Have an option to add the pull request URL to the deployment notes
2. Have the capability of add reviewers (users from the git repo) into the Pull Request5 votes -
Add a tab for Items that the Items I Selected Depend On
It would be so cool if there could be a tab that shows all the items that my selected items depend on. It would be much easier to review / select them then the way I do it now, which is expanding each item in the Selected Items tab to check for things I need to add.
Thanks!
5 votes -
For Deleted components, "Changed On" date should be date component was Deleted
After doing a major changes in an org, one can be left with a lot of deleted components to deploy. In the comparison view, they don't show up as expected. The Changed On" date isn't the date deleted. It uses the last modified date in the destination. So deleted something last week could up as last modified 2 years ago.
Ideal: Gearset would to get the Setup Audit Trail via API and display the actual deleted date of deleted components5 votes -
Modify the "Changed On" drop down filter groupings to round to the nearest day, rather than the exact time the change was made.
It would be helpful if in the "Changed On" dropdwn filter if it grouped it into days, rather than the exact time the change was made. Also, if there were preset groupings like "Today","Yesterday","Last 7 Days", etc.
5 votes -
create a compare/deploy function for data similar to metadata
having something like new/different/deleted for data (so we can compare, say, products vs new product options or features) like we do for metadata
5 votes -
Save deployment analysis suggestions and list of test classes
In order to make deployments more repeatable between orgs please allow a way to save the selection of deployment analysis suggestions an d list of test classes with a package. With a large package it can be difficult having to document or remember the same selections used in deployment to UAT org for Production deployment.
5 votes -
view deployed components live
Show live the components deployed during the running of a CI/CD Job.
Like:
deploying class abc.......
deploying class xyz.......
deploying lightning Component abc.......5 votes -
Only display active branches when displaying branches from a bit bucket cloud repository
Only display active branches when displaying branches from a bit bucket cloud repository
5 votes -
allow a method to set up default branches.
I frequently deploy from our on premises GitLab repo. It would be great to have the ability to set the default branch it goes to. It would be one less click for repetitive steps
5 votes -
Display a custom name in Salesforce when deploying from Gearset
When we deploy a change to one of our Salesforce orgs using gearset, the name that is displayed in the "Deployment Status" in Salesforce is an ID. It would be helpful to display the name that we entered in Gearset instead of the ID so that we can easily identify the changes when looking at them in Salesforce
5 votesHi,
We have recently investigated adding this feature again, but unfortunately Salesforce still don’t seem to support being able to display custom names via the Api (or it’s a feature that’s not well documented). There are requests for adding this ability via:
https://success.salesforce.com/ideaView?id=08730000000cJdxAAE
If the situation changes then we’ll certainly revisit this. We’ll keep this post opened for other users to also add their votes but it’s currently out of our hands as to when or if it can be added.
Regards,
The Gearset Team
-
Provide an option to run Aura and/or LWC testing before deployment
I don't think that very many people are actually creating Aura/LWC tests yet, but they really should be.
Since SF doesn't require them like it does for Apex, if we decide that those tests ought to be run before deployment, it would be great to have Gearset run them. This will help us to make sure they are run before every deployment instead of relying on developers remembering to do it manually.
5 votes -
Add default compare filter - Code changed by me today, changed by me last 7
A super common comparison done by a developer is to see only the Apex changes done by that developer today , or in the last x days
Since the last changed dates on Apex (VF, triggers, components) is super reliable whereas it is useless on Custom Field/Workflow), the suggestion applies only to Apex or code-type changes
Gearset would fetch only those code items changed in the last x days, then present in the difference viewer the changes pre-sorted in descending date order
This feature would eliminate multiple clicks just to deploy a handful of recently-made code changes in the comparison…
5 votes -
Possibility to deploy to another sandboxe when a ci job passed
When configuring a CI job, we need an option to set a deployment to another sandboxe when the deployment or test classes run successfully in the current CI Job.
Ex: when a push to a branch on VCS triggers a CI job to deploy to a sandboxe like QA (with test classes run), we also have the possibility to set an auto deployment to staging sanboxe when the the job on QA passed successfully.5 votes -
FLS selection for Source control
while deploying a field to source control. we just want to move profile FLS of that only field. FLS was not displayed on the components drop down of profile. we are only able select profile so that whole object's FLS are getting deployed to the Source Control.
5 votes -
Allow option to select certain test classes to NOT run. Include an exclusion list of tests not to run
When deploying code, it would be nice to have an option of having an exclusion list of test classes to not run.
5 votes -
Please, please, please get US FedRAMP approval.
The ability to use this product for CI/CD and various other use cases in the US federal space would be a huge win for many agencies. I know the FedRAMP process is quite arduous, but the contractual potential here is pretty massive.
5 votes -
Add deployment support for Macros
Macros deserve to be added to source control yet there is no way to do this with Gearset:
1) Data feature (paid add-on) doesn't deploy to/from source
2) PRO/Enterprise can't source/target deploy Macros because it is not available with the Metadata API.Since macros represent some debugged logic, managing in source control makes sense. Curiously, SFDC has chosen to make Documents available via Metadata API but not Macros
5 votes -
Trust Site
Right now, Gearset is down and we cannot use it. It would be good to have a trust.gearset.com site that shows what is going on and what the team does to fix the issue...
5 votes -
Allows admins to limit the available branches of a repository
When connecting a source code control system, quite often an integration user account is used that may also be used for other parts of the enterprise. Please allow admins to restrict the available repositories and branches so that users can only run comparisons for the branches they should actually have access to.
5 votes -
Access to Jira custom fields
we have a custom field we use that ties to a release number. It would be great if as an additional option to selecting tickets, access this field, set the value (in this case our release number) and have gearset pull all related requests in.
5 votes
- Don't see your idea?