Dataset composite chan count correct too. There is nobody tracking DatasetRGBChangedEvents that get hatched by dataset.setMerged(bool) though. (Wrong - DefaultDatasetView tracks those events and looks correct - I might just be on the wrong track here).

Anyhow what was happening was that DefaultDataset::setRGBMerged() was generating a rgb change event before changing its internal status. The event was getting handled immediately and interested parties who queried the dataset got the wrong information back.

The synchronization job between GitHub and code.imagej.net runs once every 5 minutes. So if you push to GitHub and then immediately update a ticket with the commit hash, it will not be active for a short time.