Enhancement

Label names in chatwoot only support alphabets, numbers, hyphen and underscore.
At the moment the available validation doesn't show the user any errors, which would leave the user confused.

So let's add a validation error describing this behaviour

Current behaviour

<img width="1273" alt="Screenshot 2020-10-02 at 4 29 03 PM" src="https://user-images.githubuserconten

Problem
This query could be made more efficient. We currently fetch all conversations ordered by :inserted_at, while in the UI we display them based on how recently a message was sent within it (i.e. message.sent_at).

Solution
Optimize this query to order the results by the most recently sent message associated with the conversation.

It might also be helpful to write a query to

I'm submitting a ...

• bug report

What is the current behavior? [REQUIRED]

• If username in DB is lower-case but user used upper case to log-in, the server rejects his first packet due to ticket mismatch.

Steps to reproduce [REQUIRED]

1. Create user with lower-case (eg. helloworld)
2. Login with upper-case (eg. Helloworld)

What is the expected behavior? [REQUIRED]

User

Tailor shells out to oc, and expects a valid session (which is checked via whoami). If there is no valid session, it would be nice if Tailor would exit with a special exit code so that downstream scripts can respond well to this case.

ref opendevstack/ods-jenkins-shared-library#460

FYI @clemensutschig