I Would like to have the possibility to convert any script (existing or new) into a task.

Currently it is only possible to open a single editor on one document, or to view one document and edit another, but it is not possible to copy json from the viewer window to the editor.

It would be incredibly useful to be able to work with 2+ editor/viewer windows at the same time.

Currently we must copy a document into another editor, like VSCode, to be able to copy sections into a Studio3T editor window or to work on two or more documents at the same time.

Having a migration task mapping in a computer with studio 3T is great until the owner leaves on vacation or the computer fails. When critical company's commitments rely on that migration task mapping then it must be possible to export and import it into a different studio 3T license.

Suppose I have a collection named 'group'. Currently, I am unable to execute a SQL query on this collection as this is a reserved keyword in SQL and, though, manipulations like using ['group'] in SQL query don't throw any error, no result is fetched either

When editing a document as JSON (ctrl+J), it is a modal window, and we can't do anything else on mongo while this window is open.
Moving to an another document to make some copy/paste, or view data on other documents while editing the first one will be great.

Finding Date datatype is hard to choose correct value, You should make datetime picker for this datatype. It should be more friendly

We have a lot of different databases on a cluster.
For security reason and as part of our naming convention databases are a combination of prefix and ID string.
We would like to be able to add an alias to those databases so that the right database can be quickly identified.

I don't think maybe when you upgraded your SSL as referenced in this post (https://studio3t.com/whats-new/ssl-protocol-security-upgrade/) you didn't catch all the edges.

I can't get newer versions of 3t client to connect to a replica set via x.509. Even with "allow invalid hostnames" checked. The "discovered" entries for the replica set are contained in the SAN part of the cert presented by each node. Mongo v3.4, same URI and certs connect just fine with older MongoChef 3.6. Happy to send along the certs and connection uri.