Jonathan Flatt
My feedback
42 results found
-
3 votes2 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
An error occurred while saving the comment -
9 votes
-
3 votes0 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
-
1 vote
-
82 votes
Merging differences between Apex classes and VisualForce pages is difficult to do automatically due to the understanding required by the developer. For differences between two orgs in other object types, Gearset helps you sidestep that with our granular comparison results. This blog post explains more: https://gearset.com/blog/merging-salesforce-metadata
-
4 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
-
14 votes5 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
An error occurred while saving the comment This would be very nice, or be able to configure limit which sandbox/branch merges add a jira comment, it may be nice to know that something is in our integration environment.
-
4 votes
-
2 votes
-
2 votes
-
3 votes
An error occurred while saving the comment The notification I received today had the subject "Production Metadata Changes - no changes detected", but the body said the job "Failed comparing your organization." I typically ignore the no change notifications but I would like to be alerted of failed jobs. Failed jobs should have a distinct subject line alerting of the issue.
-
3 votes
-
1 vote
-
3 votes
-
4 votes
-
5 votes
-
3 votes
-
14 votes
-
4 votes
-
3 votes
An error occurred while saving the comment At least in bitbucket, loading the repositories on the compare and deploy page takes around 10 seconds. 99% of the time we'll be using only a single repository. Being able to set a default repository and perhaps on the page allow the user to change the repository and only then retrieve the repositories from VCS.
This would allow us to take advantage of Bitbucket's rate limit increases: https://support.atlassian.com/bitbucket-cloud/docs/api-request-limits/ which are only available by using a "workspace, project, repository access tokens for authentication or make requests through programmatic access via a Forge app."
I believe this would alleviate a major pain point we've been experiencing due to being rate limited by bitbucket. These rate limits are hindering our ability to scale up our CI/CD pipeline.