Mantas Masalskis

@YetAnotherGerrit it's not allowed to remove a state (or priority) via UI. I doubt it's worth to add this limitation to command line. If someone is determined to shoot himself...

Note from live discussion with @YetAnotherGerrit . Technically it's not possible to remove the state. But it's still possible to change the type of it. Effectively having a system without...

So if I remember correctly we have 2 issues in my old branch: - `merged` state cannot be removed, but type can be changed. So we should prevent changing a...

@YetAnotherGerrit feel free to start a review app in https://git.zammad.com/zammad/zammad/-/merge_requests/8712/pipelines when you're ready to test. I just rebased it, but if you'll test sometime later, rebasing and starting a fresh...

I could see two possible migration paths: a) Rename oldest `merged` state to `merged`. Then change newer `merged` states to `closed` type. b) Rename oldest `merged` state to `merged`. Then...

> Another question if we go the "read only"-route: can we prevent changing the state via Console/API or will this be a front-end restriction only? Yes, it'd be on console/api...

Sounds good to me

I've a feeling such change would be confusing and have unexpected results. This may open a pandora box of querying among ticket articles in a single ticket. Or we could...

Looks like Microsoft Graph API has multiple throttle styles. Some limits have retry-after header and we can use that. But other limits show up as dead-end errors without `retry-after` header....

> > But other limits show up as dead-end errors without retry-after header > > Do we have the information which errors do not have a retry limit? Do you...