I have a question about the syncing of tickets. The ticket system is highly configurable, you can add fields in the table and change the forms. But it seems these changes aren't synced (or I did something wrong). Is there a reason for this or is it just something that nobody had done yet?

The ticket setup is site-specific. It is not part of the immutable history of the project. You can sync it, but there is a separate command for that:

fossil configuration sync ticket

Ah, thanks for the tip, I try it out later.

In my old copy of my test.fossil it somehow didn't work (probably because I had tinkered with it locally), but a fresh clone worked (and already on the clone) and with reverting some to default and trying fossil configuration pull ticket it got again the changes from the server. Thanks, this is helpful knowledge.

Strange to hear... Given tickets are listed in types of artifacts on fileformat page, I always thought it is also part of (and thus better than Git in this are also). May be some plans to do it?

Strange to hear... Given tickets are listed in types of artifacts on fileformat page, I always thought it is also part of (and thus better than Git in this are also).

The tickets are part of the artifact record. The ticket subsystem configuration is not. There are no plans to SCM-version that particular state, just like the site skins and user lists are not versioned.