Set how urgent a preview comment is
Marks a comment urgent, high, medium or low. Most comments never carry one.
Its own operation because it is its own register. priority_at_ms is
compared only against the stored priority’s stamp, which is what makes
a priority and a status set in the same moment from two machines both
land: neither write is measured against the other’s clock. A write
carrying an older stamp is discarded and answered 200 with the comment
unchanged, exactly as a losing status write is. An equal stamp is taken
by the incoming write, matching the desktop.
priority may be null, and a null is not an error: it says nobody has
judged the comment, which is where every comment starts. The stamp
still travels with it, because a cleared priority carrying no stamp
would lose to a later write holding an older one and quietly restore a
judgement somebody removed.
A thread that belongs to a work item is not writable workflow here.
This returns 409 with the current comment in
error.details.preview_comment, and the work is changed through the
work item instead. Draining is how a company reaches that state: a
thread a client is still executing is never linked to work. A thread
that belongs to no work behaves exactly as it always has.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Id of the theme the comment belongs to.
Client-generated id of the comment.
Body
Response
The comment, with the priority stored or left as it was.