Jonathan Flatt
My feedback
41 results found
-
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
Jonathan Flatt supported this idea · -
4 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Jonathan Flatt supported this idea ·
-
14 votes5 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
An error occurred while saving the comment -
4 votesJonathan Flatt supported this idea ·
-
1 voteJonathan Flatt shared this idea ·
-
2 votesJonathan Flatt shared this idea ·
-
1 vote0 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Jonathan Flatt shared this idea ·
-
3 votes
An error occurred while saving the comment Jonathan Flatt commentedThe 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.
Jonathan Flatt supported this idea · -
3 votesJonathan Flatt supported this idea ·
-
1 voteJonathan Flatt shared this idea ·
-
3 votesJonathan Flatt supported this idea ·
-
4 votesJonathan Flatt supported this idea ·
-
12 votesJonathan Flatt supported this idea ·
-
5 votesJonathan Flatt supported this idea ·
-
3 votesJonathan Flatt supported this idea ·
-
14 votesJonathan Flatt supported this idea ·
-
4 votesJonathan Flatt supported this idea ·
-
3 votes
An error occurred while saving the comment Jonathan Flatt commentedAt 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.
-
1 voteJonathan Flatt shared this idea ·
-
21 votes
An error occurred while saving the comment Jonathan Flatt commentedAgree with Jason's comment on bypassing the promotion pre-validation option in the CI job settings. It would save a considerable amount of time in busy orgs.
Jonathan Flatt supported this idea ·
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.