a-tze

Once there was special support for progress here: https://github.com/crs-tools/tracker/blob/master/src/Application/Controller/XMLRPC/Handler.php#L522 Maybe you ressurrect this feature. Progress should not be stored as a regular ticket property, and the "progress" attribute of a...

Ok... if you really need this kind of information in the tracker itself, then maybe an optional parameter for the SetTicketProperties method that disables logging all together?

Without knowing the whole use case, I really think those things belong into a MQTT broker or similar. However, my personal suggestion that might serve other purposes as well is...

Therefore I suggest it not being called properties at all, but give it a different name, store it somewhere else and then it's by definition not important.

@Garionion maybe this is better solved by using something like mqtt?

Firefox 52 on Win and Linux, possibly related error messages in the browser console: 11:17:53.542 Content Security Policy: Die Einstellungen der Seite haben das Laden einer Ressource auf blob:https://tracker.c3voc.de/6a51a6fd-6503-4968-82af-17f7d8507db4 blockiert...

I meant version 57, sorry.

Yes, there is NoScript, but currently on "All scripts allowed". On Linux there was no NoScript. Other users also agreed that the link was infunctional for quite some time.

You would reset it to staging.. and yes, the terms don't match and it's a huge change in concept. However, we're talking about things to be done on METAdata, and...

The "metadata changed" problem should be solved by using some hash. There is similar logic in the Auphonic worker. The hash can be stored as a regular property and later...