New status format

[n1xqe]

Microservice

report

Priority

Normal

Issue

Get a uniform response with the exception of /ticket/list (get)
There are more then one format for errors, etc..
new format (example 200):

{
    "status": "OK",
    "code": 200,
    "timestamp": str:time,
    "path": str:path,
    "msg": str:msg
}

[RedstoneMedia]

Can you PLEASE for the love of god provide a real priority its not that hard and it would help us allot.

[adrian-goe]

@RedstoneMedia Please use the colloquial language

[JavaDerg]

I think you don't understand the definition of priority in this case.
By Priority we mean now what we should prioritize about the issue, but how important the issue is in general.
If we have a issue that lets a user download the entire user database, thats CRITICAL.
If 2auth (if we implement that) isn't working properly, but that doesn't make the site unusable, that's High.
Most issues are Normal because they are not super important but also need to be done soon.
And then we have Low for stuff like enhancements, like possible new features that maybe be interesting in the future.

@RedstoneMedia my word choises in an earlier issue weren't particularly nice, and I probably shouldn't have reacted that way but we shouldn't make this Repo like StackOverflow.
Truth be told I have the bad feeling @iiestIT isn't very capable of English so we should respect that.

@iiestIT Please try to be as precise as possible and if you need help writing something in English, write the parts you aren't sure about in German a few lines under the actual content and tag the Issue with needs-translation. Otherwise we can't help you.

[n1xqe]

Ok, well. I misapprehend that. @post-rex Could you make a list of that (in a shorter version) and pin it in dc or write it into the readme?