What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

When designing database schemas using MongoDB data modeling diagrams, it is difficult to document the purpose of individual fields. Currently, field properties include details such as the field name and data type, but there is no dedicated description or note field to explain the field's purpose, business logic, or usage.

What would you like to see happen?

Describe the desired outcome or enhancement.

Please add an optional Description / Notes property to each field in the data modeling tool.

The description could be entered in the field properties panel, alongside the existing field name and data type. It would also be helpful to display the description as a tooltip when hovering over a field in the diagram.

Ideally, these descriptions should be saved with the schema and preserved when exporting or sharing the data model.

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

This feature would improve schema documentation, make data models easier to understand, and help teams collaborate more effectively. It would be especially useful for large databases with complex business logic, where field names and data types alone do not provide enough context.

It would reduce the need for separate documentation and make the data modeling tool more useful for both developers and database designers.

What steps, if any, are you taking today to manage this problem?

Currently, we manually maintain separate documentation and rely on descriptive field names and comments in our code to explain the purpose of each field. This makes it difficult to keep documentation synchronized with the data model and requires additional effort when reviewing or modifying schemas.