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.
1240 results found
-
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 -
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.
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 -
enable using a Repository Access Token instead of a Service Account
I would like to be able to use a repository access token instead of a service account to connect to VC (Bitbucket in my case). https://support.atlassian.com/bitbucket-cloud/docs/repository-access-tokens/
The main benefit for me would be the ability to conveniently authenticate while maintaining a high level of security, even in situations where corporate change management policies and SSO requirements can be cumbersome.
1 vote -
Unsubscribe from commit emails
Choose to unsubscribe / subscribe from commit emails (success and or failures) in gearset setup in order to avoid generating unwanted emails (and their PDFs) for each deployment (and save a little CO2 along the way).
1 vote -
Improve visualization of multiple features being simultaneously worked on in a single developer sandbox.
Currently, one must select (or create) a single feature+branch in the developer sandbox. The pipeline view only shows 1 active feature at a time. It would be nice visually see all of the features an individual developer is working on/assigned to.
1 vote -
Gearset Pipelines Sandbox Environment
In order to test new Jira webhooks, GitHub actions, and any other release management changes,
We would like a Gearset sandbox environment where we could test release management changes like new/updates to Jira webhooks, GitHub actions, and other related changes.
1 vote -
Display pipeline webhook errors in Pull Request details
Scenario:
- Feature branch created, commits added, Pull Request opened and pushed part-way through the pipeline.
- Pull Request has merge conflicts on one of the environments. Conflicts are addressed, but (let's say) PR fails validation so it is not promoted.
- New commit is added to the feature branch.This commit will generally fail to propagate into the above mentioned PR branch (triggering a webhook error). It would be GREAT if that error were somehow displayed on the PR details screen.
1 vote -
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.
1 vote -
Precision Deployments for Lightning Web Components
It is very much required to have Precision Deployment for LWC components as it is common to have multiple developers working on same LWC
1 vote
- Don't see your idea?