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.
360 results found
-
Add a "Clone Package" to the Validate packages tab
Allow users to clone a validated package just like that can clone a deployed package.
3 votesWe’ve now added a dedicated Clone Package action to the validated packages table for Enterprise users.
-
Add the ability to filter by Date to Data Deployment
It would be very helpful to some processes I run if I could do data deployment filtered based on date - date created specifically. I am trying to migrate some test data from Production to QA/User Testing and I get duplicates now. A filter on created date would solve the problem entirely.
1 vote -
Add the Deployment Friendly name to the Deployment Report
On the deployment report pdf can we add the deployment friendly name above the deployment notes.
3 votesThis has been completed and friendly names will now appear on the deployment report.
As always, feedback welcome!
-
Commit-by-commit deployment
As you are giving an option to trigger the CI job based on repository commit, it would make more sense to only compare the source and target based on the commit items and consider the commit changes for deployment based on your selection of either new, modified or deleted and the comparison filter(which can be optional in this case).
This will help in reducing the chances of overriding the changes of other teams working in a shared environment or an environment not in sync with the branch.
There can be other scenarios where we maintain managed package items in the…
43 votesThis was released on the 23/03/2021. Documentation is on https://docs.gearset.com/en/articles/5069914-delta-ci
-
add the ability to deactivate an invitation.
Hi, I think the system needs the ability to deactivate an invitation. I sent the invite to the wrong email and I don't see any way to deactivate the invite. other than copying the link and signing up with my account. I realize it expires after 3-5 days but i sent it joe123@gmail when I should have sent it to joe124@gmail and i just don't want to risk an unknown user getting into our metadata.
2 votes -
Allow us to configure a push notification when comparisons are done.
It would be great if we could configure a notification when a comparison completes. Sometimes comparisons take a long time!
7 votes -
When creating a scratch org, allow a user to define the expiration number of days
Currently, when creating scratch orgs, the system automatically sets the expiration to seven days. However, scratch orgs can last as long as 30 days. Would it be possible to define the expiration number of days during creation?
2 votes -
Ability to change the value of a field on import
Price Rules have Price Conditions and Price Actions and sometimes Lookup Queries hanging off of them as related objects. Some of the price rules wouldn't get created because there is a field called Conditions Met and it equaled Custom. If we were doing this migration via data loader, I would set those records to equal All for the value just to get the price rules in. Then we would load the Price Conditions. Then we would do an update to the price rules to set it to what it should be - Custom. We cannot save the record initially with…
1 voteYou can now deploy Price Rules and Price Conditions when Conditions Met is set to Custom. You’ll need to have either All or Any set as the default picklist value for the deployment to work.
It’s also possible to deploy Product Rules and Error Conditions, and Approval Rules and Approval Conditions.
-
Allow default repo to be set in Manage Connections and use in Comparison
This does not appear to work.
- Setup connection to source control GitHub that your user credentials includes multiple repos (in my use case, there are about 100)
- Do a Comparison, in the target list of repos, you will see all 100
- Select your repo (say repo #77). Do the Comparison
- Logout
- Login. Repeat step 2.
RESULT: repo#77 is not defaulted. You have to reselect it.
Either fix the aforementioned issue so the repo you most recently used is 'sticky' or allow specification of a default repo on the Connections page for each repository type.
1 vote -
Fix Keyboard shortcuts for selecting differences
When I have a lot of changes to review I'd like to use arrow keys to go up/down and expect "space" to toggle the checkbox for that. However the checkbox focus doesn't move with the highlighted row - so it doesn't work :(
1 voteThis has been completed and Gearset now has the shortcut keys you’d expect.
Thanks,
Kevin -
Sort order of Orgs ignores friendly name
If you have friendly names for your org connections, the list of orgs presented on the Comparison page ignores these and instead sorts on sandbox name. Since the lines show friendly name left most; this is not natural to the human to see things out of order
Example
OrderFix (joe.blow@foo.com.story003)
Invoicing (joe.blow@foo.com.story010)
AlphaTest (joe.blow@foo.com.story091)when what the eye wants to see is:
AlphaTest (joe.blow@foo.com.story091)
Invoicing (joe.blow@foo.com.story010)
OrderFix (joe.blow@foo.com.story003)1 vote -
Add a "Clone package" button to the Deployment Results page
My workflow is currently to deploy a change, browse to the deployment history to find my deployment, and immediately clone the deployment for another environment. It would be really nice if the clone button were available upon a successful deployment.
5 votes -
Allow editing all CI Job Fields
One should be able to edit all the fields on a CI Job, especially the source and destination fields.
2 votes -
Upgrade to PMD 6
PMD 6 includes useful stuff like allowing annotations in the code to suppress warnings. It would be great to be on that version.
Stephen told me via the support chat that it wasn't simple to just upgrade, so I thought I would submit it as a feature request.
2 votesHi Aidan,
We’ve now upgraded to PMD 6.3 which includes support for suppressing warnings.
Regards,
Stephen
-
After choosing source/target connection: show friendly name.
When we are selecting source/target we can see the friendly name in the dropdown list.
After the selection is made we can see only the username. It would be easier visually confirm that correct connections are are selected if the friendly name was shown next to the username.
1 voteThis is now completed, and friendly names will appear in the dropdown where you select the org
-
Have a way to exclude objects from comparison
Before using Gearset we used the Force.Com migration tool. We got to learn that several things just can't be deployed to sandboxes so we always excluded them from source control, or learnt to not merge them.
Gearset has filters which mean you can specify things to include, but it would be nice to have things it would automatically exclude for you (i.e. not show in comparison). Some of these it already knows not to try and deploy. Things like
Admin.ProfileUserPermission.EditBillingInfo
Admin.ProfileUserPermission.ManageSandboxes
etc.but there's a few other random pieces that I have to remember to untick each time or deployment…
9 votesYou can now exclude specific items in your custom metadata filters in a similar way to how you include specific items.
This won’t cover some cases, such as excluding subcomponents like specific user permissions within a profile, but for those cases let’s open a new specific feature request.
-
Ability to Clone Button on the Draft Deployment page
Can you create a Clone Button on the Draft Deployment page similar to the Clone Button on the Deployment History page? Some times we collaborate on a deployment and one user will take over. We want to be able to deploy the package as the current user, not the original one that made the draft.
10 votesThe ability to clone draft deployments is now available on the enterprise tier.
-
Active Link to Deployment Destination
When you finish a deployment you get a "Deployment Summary" screen that has handy details. It does not, however, have a link to the commit/branch in Github or other site where the destination ended up. I have to jump to my Github page and refresh instead of having a direct link. Yes, it's a tiny feature but is useful for a Gearset newbie like me.
1 vote -
Validation-only deployment for CI
Add the option to for CI to run validate-only deployments
2 votes -
Clickable Jira Request within Deployment Report
I would like the ability within the deployment report to make the jira tickets clickable. That way a user could simply click the ticket reference to navigate directly to the request.
1 voteThe Gearset has made this feature available for Jira tickets and Azure DevOps work items, thank you for your suggestion.
- Don't see your idea?