Eero Lampela

@NikitaM This speeds up random ticks in Minecraft. It is completely different from the actual tick speed of the game. 
This is WAI, zombie pigmen spawning in portals is based on random ticking, each portal block has a chance of spawning a pigman when random ticked.

This is very likely due to the fix for translocation causing some unwanted side effects.

Still happening for me in 1.12.2 and in latest 1.13 snapshots (18w07b). Issue should be reopened.

This is not a bug. The bug where random ticks would effect liquids was fixed, leading to this. This is incorrect world generation. Liquids should generate already flown, like they do in 1.12.2. That is the bug, not that liquids are not effected by random ticks.

Confirmed for all versions since 1.9.

Environment should be "any" instead of java 8 windows 10, this is caused by the fire block not appearing, which is caused by the fix to mc-4923.

”If you need to drop the block, push a glazed_terracotta, you can only push the block and not pull it” Problem is, this is not possible most of the time. That is completely ridiculous to even suggest that this behaviour could be compensated by something like that. I would say that in 95% of the cases glazed terracotta cannot do the same thing as sticky piston block dropping. This is becouse most contraptions are designed to be reusable, and you need a second piston pushing the terracotta in place.
One thing you can rely on, is that the community will rely on this behaviour to stay, and use it accordingly. It is just too important and way too useful to not to use.
I would say that this behaviour is the single most important bug for redstone, much more important than quasiconnectivity. We could propanbly do about 50% of the things possible with quasiconnectivity without quasiconnectivity, but if this gets fixed, i would say that at least 80% of all redstone ever made that uses sticky pistons will be broken, beyond repair. Note that this does not only mean all piston doors, all treefarms and all flying machines, but simple binary counters, simple logic gates based on observers and sticky pistons, and overall basically everything that uses sticky pistons.
If there are three things that are important for Java redstone, they are (in my opinion, and in order)
1. Sticky piston block dropping, since this behaviour is so fundemental in the redstone system as we know it, i would estimate that more than 75% of all redstone ever made would be broken without it, which of at least half would be broken beyond repair, offering no alternative.
2. Quasiconnectivity, since this again is something fundemental that a lot of contraptions are based on. If this gets fixed, i would estimate that about 50% of all redstone would be broken without it, which of about 50% would be broken beyond repair.
3. Deterministic update order, at least to some extent. This allows for so many intresting bugs and quirks to be discovered and used reliably

Sorry for the wall of text, and i hope you get my point. This behaviour is too important to fix. If this gets fixed, not only the tech community will be screwed up, but also everyone who has ever made anything that uses sticky pistons, that is the whole redstone community. The broken contraptions are counted with 8 or more digits. If it gets fixed we can just move to bedrock edition, no point in playing java any longer. I would seriously suggest making it an offical feature. It is just way too important to be broken.

Then why was MC-5726 marked as WAI? And why has that not been updated if this is intended behaviour? It should be resolved, not working as intended, if this really was intentional.