Jonathan Flatt
My feedback
54 results found
-
4 votes
Jonathan Flatt supported this idea ·
-
2 votes
Jonathan Flatt shared this idea ·
-
3 votes
Jonathan Flatt shared this idea ·
-
3 votes
An error occurred while saving the comment Jonathan Flatt supported this idea ·
-
3 votes
Jonathan Flatt supported this idea ·
-
1 vote
Jonathan Flatt shared this idea ·
-
3 votes
Jonathan Flatt supported this idea ·
-
4 votes
Jonathan Flatt supported this idea ·
-
5 votes
Jonathan Flatt supported this idea ·
-
3 votes
Jonathan Flatt supported this idea ·
-
14 votes
Jonathan Flatt supported this idea ·
-
4 votes
Jonathan Flatt supported this idea ·
-
1 vote
Jonathan Flatt shared this idea ·
-
23 votes
An error occurred while saving the comment Jonathan Flatt commented
Agree 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 ·
-
to add an option to not to run unit tests validation in CI job in case there are no changes detected
2 votesJonathan Flatt supported this idea ·
-
2 votes
An error occurred while saving the comment Jonathan Flatt commented
It would be nice to have a revert option in Gearset that wouldn't open a PR to the next environment.
-
7 votes
Jonathan Flatt supported this idea ·
-
2 votes
Jonathan Flatt supported this idea ·
-
6 votes
Jonathan Flatt supported this idea ·
-
7 votes
An error occurred while saving the comment Jonathan Flatt commented
Would be very useful. When releases get large it's quite cumbersome to abandon a release and re-create.
Jonathan Flatt supported this idea ·
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.