Skip to content

Share your ideas with us

75 results found

  1. Remember field location when changing views

    When switching from table view to tree view, open the tree to the location last viewed in table view. For example, if your viewing path in a document is profiles.merchant.business, when switching to tree view, the disclosure triangles should be open for profile, merchant and business, so you would be placed at the same view of properties/values you were observing in the previous view. The inverse should hold true if switching from tree to table.

    If switching to json, the focus should bring you to the last property viewed.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Support copy/paste from Script History

    The "Script history and script browser" is a modal form, this makes it cumbersome to use. The Script history stores only single commands.

    If you like to use multiple commands, then you have to copy the script from Script preview, close the form and paste the code into IntelliShell. Then open Script history again, scroll down, find next command, copy next command from Script preview, close the form, paste it into IntelliShell and so on.

    When you click on "Load" then the current IntelliShell is cleaned and your existing code is deleted. You cannot select more than one command and…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Query Code for Python 3 without unicode prefix

    When generating query code for Python in the aggregation editor, it generates Python 2 syntax for Unicode strings (u"$match").

    There should be an option to also generate for Python 3 without these prefixes (since Unicode strings are now the default).

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Put the exact match at top of the search results in the collection search.

    I have a collection called "consumer" and a lot of other collections with the name that includes "consumer" in the middle ("consumer", "appconsumer_profile", ...").

    And when I search "consumer" in the search bar other collections take the first results as they are lexicographically higher order, making me have to scroll down to get to my collection. IMO exact matches should take the top spot.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Find usages

    It would be great to be able to right-click on any collection or view and "find usages." This will inspect the aggregation pipelines in the database, look for any use of the collection or view, and display the list of results. For example, here are places to look:

    1. A collection is the "View on: [collection]" for a view.
    2. A collection / view is used in the $lookup stage of a view via the "from" field.
    3. A collection / view is used in the $unionWith stage of a view via the "coll" field.

    This will help developers learn about it's dependencies…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Separate settings for initial page size and query result size

    Appearance and behavior > Appearance > Table, Tree and JSON views > Initial page size when showing result documents

    The above already exists but the minimum value is 1. This is problematic for developer experience. Setting it to 1 will remedy the issue of loading collections with large documents, but every other collection will also only show one result. The user story would be to increase the number in the dropdown.

    The proposal is that either:
    - an option to not load any data initially but still have default query result size
    - separate settings for initial load result size…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. You are magical. A few ideas.

    Hello!

    Thank you for the wonderful program, which is an integral part of our development tool.

    Here are some suggestions:

    It would be great if we could get integration with ChatGPT for generating aggregated queries.
    The ability to program dashboards based on developed queries for visualizing graphs. Usually, I use your program to get certain data. But it would be great to have the functionality to receive graphs and indicators without leaving the program. Something similar to the dashboard in Elasticsearch.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. AI Helper custom Base URL

    Allow us to set a custom base URL for the AI Helper to point it towards another OpenAI compatible server. for example LocalAI ( https://localai.io/basics/getting_started/#clients ) or Azure AI.

    That would allow us to use the AI Helper while sending the data to our own models and private OpenAI instances.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Support uploading JSON "explain" output and render it visually

    In cases where I don't have access to a DB (e.g., because its in production) I have to ask our devops team to run a query with an explain for me. It's not possible or practical to have that team to use Studio 3T so they just send me the raw JSON explain output. It'd be nice if there were a way for me to upload that output into Studio 3T and have Studio 3T render that visually for me.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Export to csv - add option to insert a BOM.

    If Excel is associated with csv files it will open them on double click, but it loads data as ASCII and therefore messes up UTF8 encoded data!! However, if the csv data is proceeded by a BOM Excel will interpret the data correctly as UTF8.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Selected table row text is unreadable in dark theme

    The selected table row background becomes #c2ced7 but the text colors are designed for a dark background.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Show the full name of indexes in the "explain" window

    My index names are long. It'd be good if in the explain window I could hover over an index "box" and have a tooltip popup and show me the full name of the index.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Support more standard macOS text editing keys

    In most macOS text editing contexts, the following keyboard shortcuts exist:

    ^A: move to start of line
    ^E: move to end of line
    ^D: Delete the character to the right

    However they don’t work in Studio 3T IntelliShell windows and I don’t see a way to enable them in the keymap.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Explain plan seems to ignore .special or .hint on find queries

    I am trying to provide the hint and either atlas is not using the index I am suggesting or the shell is ignoring it when doing an explain. The explain is showing that it is using a different index.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Enhanced static checking in Intellishell

    The scripting process in Intellishell would be MUCH faster with static checks that identifiers have a value.
    For example the editor does catch the following very, very common mistake;

    // declaring some variable
    const someVar = db.getCollection('someColletction').findOne();
    // erroneously referencing some other (undefined) variable since the user misspelled it
    print(someVarr);

    Even worse, the misspelled identifier could have a value stored in the interpreter (from a previous execution) even if it doesn't appear in the current version of the script. This is a problem since the code could actually execute, and dangerously give unexpected results (for example, the user updates documents…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Show collection name on Tab title by default

    When open several tabs to edit/view different collections, it's hard to know which tab is for which collection.
    I think its good to show current collection name on Tab title by default, to help users recognize.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Make fs.files (and fs.chunks) data deletable with a task if the _id is not referenced in any collection

    Make fs.files (and fs.chunks) data deletable with a task if the _id is not referenced in any collection and run it every day part of scheduled task within 3T.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Please do not write into the user home directory without explicit permission

    Currently 3T writes settings and other things into the user home directory under .3T, .swt and .cache (on macOS; possibly different on other systems). This clutters the home directory and is therefore generally discouraged.

    On macOS specifically, Apple user interface guidelines dictate that settings should go into the folder ~/Library/Preferences, and cache files should go into ~/Library/Caches. Similarly, on Linux the generally agreed-on guideline is to adhere to the XDG Base Directory Specification.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Grouping of Tabs based on some name(JIRA ID)

    Hi,

    On regular basis I spend lot of time on DB for investigating multiple JIRA simultaneously.
    Some this when I am working on a JIRA, in mid of investigation i used to get PROD issue which takes highest priority.

    The PROD bug and previous JIRA the one I am working may be related same collections(which are around 10-12 collections).

    By the time i resolve PROD issue, I end up with opening same collection multiple times with different query results.
    I need to go through each collection and its query to make sure which window should be close and which window…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4
  • Don't see your idea?

Share your ideas with us

Categories

Feedback and Knowledge Base