Share your ideas with us
727 results found
-
Aggregation editor stage operator autocompletition
Aggregation editor -> new stage -> Default stage is $match.
When you click to the the select list field, you have to always start with the$character and write the starting letter of the operator name, to "complete it" with down arrow press.All the stage operators begin with
$character so it will be nice if you'll be able to autocomplete just with the beginning letters, and add the$character on the background.Example:
writing
gro
press down arrow
in the input appears$group.I know this is the cherry on the pie, but i see…
1 vote -
Pricing could be based on usage.
We currently use Studio 3T to support some legacy projects that require us to open Studio 3T once every couple of months. For current use, licenses do not "pay off" for us.
We are happy to contribute. However, it would help us if you had a more flexible pricing option, say 1USD per hour of usage for this usage pattern.
We will open new projects that use MongoDB as a data storage backend and hopefully we will use Studio3T more.
1 vote -
Open scripts without need to select the collection every time.
Having an option to open a script without selection a specific collection will be really useful.
1 vote -
3 votes
-
Databases panel on the left focuses/switches to currently open collection tab
Database and collections pane automatically focuses/switches to whatever tab(collection) is currently open. This is really helpful when there is so many databases and tabs open
1 vote -
Databases panel on the left focuses/switches to currently open collection tab
Database and collections pane automatically focuses/switches to whatever tab(collection) is currently open. This is really helpful when there is so many databases and tabs open
1 vote -
Save default export settings
Save default export settings so we don't need to specify CSV, Clipboard, Excel, Tab, etc... every time.
3 votes -
Add one-time purchase option
Would love to have the option of paying for the product once and use it forever instead of paying annually, even if it means I will not receive updates afterward that's ok.
4 votes -
make the app work in wayland sessions on linux.
currently the app only works well on x11. when I switch to wayland the title bar becomes large and weird and the app registers random clicks on the top left corner even when I click on an item in the table view.
1 vote -
Add option to disable Syntax Check in IntelliShell
Unfortunately in version 2021.10.0 the IntelliShell was getting very bad and makes the editor useless when you have to work with longer scripts.
I don't expect an immediate solution for better code-folding and syntax highlighting. But a quick and easy fix would be an option to Enable/Disable the Syntax Check. Then I would disable it and could continue using Studio 3T.
Note, even the 30 years old VBA-Editor in MS Excel provides this option, it should be a rather small change in the code of Studio 3T.
2 votes -
Bookmarks synced with .js files
it would be nice if saved bookmarks from a query saved on a file stay synced on changes.
Ex.
Open file myquery.js
add the script to bookmark
update the file with some fix
select the bookmark and it has the new fix1 vote -
tab as selector
Basically, we came from mongo shell. We have habit of pressing tab after writing 2 or 3 letter for any db name or collection name. In mongo shell the tab will automatically picks up the correct collection name upon pressing tab. But in studio 3t I don't see that functionality and for me it is difficult to press enter to select db or collection name. It would be better if that choice is left to us. People who want to use tab as selector can chose tab and those who want to chose enter as selector should chose enter. Please…
1 vote -
Predefined queries with parameters
Let the user select for a collection a query with parameters.
Also let the user ctrl+click (or similar) on an attribute of a doc to open one of this queries with parameters (from this or other collection) with that clicked attribute as a parameter value.
For example:
On my 'orders' collection I predefine the query {_id: <param1>}
and on my 'users' collection, predefine that if I ctrl+click on a user attribute 'lastOrderId' it will open the 'order' collection and auto-run the query stated above with 'param1' being the value of 'lastOrderId'.2 votes -
I would like to check a box stating "Always proceed using Query Assist"
Frequently I am asked if I would like to proceed with or without Query Assist because "the user changed". I don't care, and I will always want to proceed WITH Query Assist.
1 vote -
operations log details
For the export unit tasks, the operations log states: source db.collection -> To another collection.
it should actually log what the target collection is.. db.collection@cluster.
1 vote -
(Robo 3T) Quto fill option for fields
Like you have in Studio 3T, it would be great to have an auto fill option for Robo as it would save time guessing or having to type the field names in all the time.
1 vote -
2 votes
-
Export to excel format (additional to csv format)
Using a true excel export format would eliminate problems with floats using a . or a , for digits separations and date format. Where excel-expecting another local date/float format. These stuff is mostly a problem outside the USA (say the rest of the world using different time formats and floating point formatting)
7 votes -
Import Task - Json - Import Source does not show path
I am setting up Tasks to import export/import collections into various test databases. The Task Edit option on Import Json does not seem to provide a facility to view the path to the import sources. This would be useful to confirm the data source is the correct one before running the Task.
2 votes -
Allow scripts to prompt for/accept input/parameters
Maybe you already do this, but it's hard to find the documentation.
We often want to run the same, fairly complicated query with different parameters, on different databases (dev/staging/prod) & compare the results.
There are a lot of ways you could support this - prompting for user input on script execution, or parameter fields above the script, or as per another suggestion, scripts that can call other scripts - so they could set initial parameters.
Or you do support something like this but it's not clear.
4 votes
- Don't see your idea?