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
-
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…
1 vote -
Allow Dev Updates to be Qued
Allow dev updates to be in a que so that you dont run into the problem of updating to many at the same time.
1 vote -
Update all Dev's button
Create a Update All Dev Sandbox button in a pipeline that allows you to quickly update all of the devs at once instead of clicking into each one.
1 vote -
Allow for different pull request messages.
I would like the ability to have different pull requests message per pull request that is autogenerated when you move through the pipeline.
Example: When I first create a pull request from dev to my next static environment the message would only pertain to that static environment. So from Dev to UAT I would include a pull request message pertaining to testing.
Then after that I would move from UAT to Staging so the message would be something about the testing and how it is complete and ready to move to staging which is our integration environment.
Then when that…
1 vote -
Cancel Comparison
I would like to be able to cancel comparison jobs so that I can totally reset the metadata selections and run it at a different time instead of making the modifications during its run time and possibly taking longer because of the changes.
1 vote -
Job Completion Percentage
I would like to see more details about the status of a deployment or validation job in the Pipeline. Right now it just says job is running. I would like to see a estimated percentage of component validated/deployed against the total. Also maybe a running time estimate.
1 vote -
Auto navigate to next conflict after resolve
After I have resolved a file/metadata component I would like it to auto navigate to the next item in the list.
1 vote -
Custom Sort Conflict files by metadata type
I would like to be able to sort conflicting files by metadata type in the conflict screen. That way I can resolve conflicts in a more organized fashion.
1 vote -
Update Slack notification messages format
Update the slack messages to more clearly define what happened in the action.
There should be a more clear title to the slack message. It should define what item was doing what. Currently that is grouped into a description which does not show on slack notifications.
CI job notifications should have a more clear "from where to where" section in the notification. Currently its grouped into the description.
1 vote -
All available branches display
Create a view that displays all active and available branches and there current commits and pull requests. That way if there a multiple branches per environment a release manager can see everything that is going on instead of having to click into each environment in the pipeline or going into git.
1 vote -
Show Auto resolved conflicts
When in the conflict resolution screen it would be nice to quickly see all files that have been auto resolved. Maybe with a icon of some sort on the left hand side next to the circle icon for resolved or not resolved.
1 vote -
Provide ability to link ADO ticket after a package has been validated
It would be great to be able to attach/link ADO ticket after a package has been validated. Currently we can only do it before click the validate button
1 vote -
Create a queueing system for the new sandbox updates process
The new sandbox updates process, replacing long lived branches and back propagation in Gearset, is a really nice feature. However, it has limitations. I have found when trying to update multiple sandboxes at once using the updates feature, Gearset can only handle a couple before throwing an error and saying it is too busy and to try again later.
I have 6 sandboxes in the pipeline all using this feature so I have to start two, wait for them to update and then start the next two and so on.
If there was a way to set up a queueing…
1 vote -
Update Jira Status when linking to a ticket in Gearset
When a Jira ticket is linked to a branch in Github through Gearset, the status of the ticket could be automated (For example, we have statuses of In Development or Ready for Pipeline which could be used) to match further with the automatic status changes when the feature deploys through the pipeline.
1 vote -
Include CPQ Favorite objects in the supported objects
CPQ includes Favorite objects as part of the package but Gearset doesn't support them. These can be shared proactively with users so they don't have to make their own Favorites. We make these in a sandbox along with new CPQ product configurations and would like to be able to push these up to production along with the new configs.
1 vote -
Let "member" create team-shared CI jobs OR let owner convert member's CI job to team-shared
I see currently only team owners are able to create Team-Shared CI jobs. When my offshore team members who have "Member" role need to create a new CI job, their only option is creating a user-owned CI job, thus missing the benefits of Team-Shared CI jobs. All of our org connections are already Team-Shared. And we already have a Team-shared VC connection too. So, it'd have been very helpful if non-owner users with "Member" role could create Team-Shared CI.
Alternatively, if that's not possible, next best thing would be - if team owners could convert any member owned CI job…
1 vote -
Let "member" re-authorize team-shared orgs connections
In our Gearset setup, we have tens of "Team-Shared" orgs, both production and sandbox. Whenever any sandbox gets refreshed, its connection in Gearset needs to be re-authorized.
Currently, only users with "Owner" role have this "Re-Authorize" option. Users with "Member" role don't have this option.
This creates a problem for my team. Since my offshore team is supposed to do these sandbox refresh and re-authorization tasks, and they can't do it unless I give them "Owner" role, and thus giving them admin privilege over the entire Gearset.
Thus, I'm looking for a way to let a non-owner re-authorize salesforce org…
1 vote -
Deploy the Name of object without truncating
Hello,
I deploy from Sandbox to Prod.
I have a custom object where the Name is 42 characters long on the Sandbox.
When I deploy, it has only 40 characters on Prod.
If I run compare, 42 on sandbox, 40 on Prod.
If I deploy again, still 40 on Prod.
I can of course change the Name by hand on Prod to 42 characters.
Thanks
Stephane1 vote -
Add support to deploy Digital Experiences (LWR) using Digital Experience Bundle Components
Similiarly to how you can deploy metadata for non-LWR Digital Experiences (Aura templates), where you can select different metadata changes individually using Experience Bundle Components, rather than deploying all your changes at once, it would be great if that option is available for Digital Experiences running on LWR (Digital Experience Bundle)
1 vote -
Team members are able to create release with no access to CI job
Team members are able to create release with no access to CI job.
"Promote changes" is gray as expected, however "Create release" works which is awkward1 vote
- Don't see your idea?