[Refactor] Notes

.github/workflows/frontend.yaml

@@ -136,7 +136,7 @@
           pip-dependency: psycopg2
       - name: Set up test data
         run: |
-          invoke dev.setup-test -iv
+          invoke dev.setup-test -iv -b multi-note # TODO: Fix this before merging
           invoke int.rebuild-thumbnails
       - name: Install dependencies
         run: invoke int.frontend-compile --extract
@@ -218,7 +218,7 @@
           pip-dependency: psycopg2
       - name: Set up test data
         run: |
-          invoke dev.setup-test -iv
+          invoke dev.setup-test -iv -b multi-note # TODO: Fix this before merging
           invoke int.rebuild-thumbnails
       - name: Install dependencies
         run: invoke int.frontend-compile --extract

.github/workflows/import_export.yaml

@@ -90,7 +90,7 @@
       - name: Setup Postgres Database
         run: |
           invoke migrate
-          invoke dev.setup-test -i
+          invoke dev.setup-test -i -b multi-note  # TODO: remove the -b option once the multi-notes migration is merged into master
       - name: Create Plugin Data
         run: |
           pip install -U inventree-dummy-app-plugin==0.1.0

CHANGELOG.md

@@ -9,6 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Breaking Changes
 
+- [#11971](https://github.com/inventree/InvenTree/pull/11971) is a major refactor of how notes are handled. Notes are now stored in a separate database table (in line with how attachments are handled), and each model instance can have multiple notes associated with it. The `notes` field has been removed from the individual models (and their associated API endpoints), and notes are now accessed via the new `/api/note/` endpoint. Existing notes data (and any embedded images) are automatically migrated to the new notes table, with the markdown content converted to HTML. Any external client applications which read or write the `notes` field via the API will need to be updated to use the new endpoint.
 - [#12507](https://github.com/inventree/InvenTree/pull/12507) calling an invalid or repeated state transition now raises a ValidationError. Plugins implementing state transitions should evaluate the PR and adapt their usage of transitions to gain the new safeguards.
 
 ### Added

docs/docs/concepts/notes.md

@@ -0,0 +1,147 @@
+---
+title: Notes
+---
+
+## Notes
+
+*Notes* allow free-form rich-text content to be written and stored against a specific object within InvenTree. Notes can be used to record observations, instructions, historical context, or any other information associated with a model instance.
+
+!!! note "Business Logic"
+    Notes are not to be used for any core business logic within InvenTree. They are intended to provide supplementary documentation and context for objects, which can be useful for reference, communication, or reporting purposes. Plugins should not use them for storage and opt for object metadata or custom models instead.
+
+Notes can be associated with various InvenTree models, and each model can have multiple notes associated with it. The user interface provides a dedicated "Notes" tab on the detail page of any model that supports notes, allowing users to easily view and manage notes for that object.
+
+### Notes Tab
+
+Any model which supports notes will have a "Notes" tab on its detail page. This tab displays the content of the currently selected note, along with a sidebar listing all notes for that object by title:
+
+{{ image("concepts/notes-tab.png", "Notes Tab Example") }}
+
+## Note Fields
+
+Each note has the following attributes:
+
+| Field | Description |
+| --- | --- |
+| Title | A short title for the note (*required*) |
+| Description | An optional brief description of the note's purpose |
+| Content | The rich-text body of the note |
+| Primary | Marks this note as the default note for the object |
+
+## Primary Note
+
+When a model has multiple notes, one may be designated as the *primary* note. The primary note is indicated by a {{ icon("star") }} icon in the note sidebar.
+
+- When the first note is created for a model instance, it is automatically set as the primary note.
+- Only one note per model instance can be marked as primary at any time.
+- The primary note is opened by default when navigating to the Notes tab.
+
+## Rich Text Editing
+
+Note content is edited using a rich-text (WYSIWYG) editor. The following formatting options are available:
+
+- **Text formatting**: Bold, italic, underline, strikethrough, inline code, code blocks
+- **Headings**: H1 through H4
+- **Structure**: Blockquotes, horizontal rules
+- **Lists**: Bullet lists and ordered lists
+- **Links**: Insert and remove hyperlinks
+- **Tables**: Insert tables; add/remove rows and columns; toggle header rows
+- **Images**: Embed images uploaded directly into the note
+
+### Inserting Images
+
+Images can be embedded in note content in the following ways:
+
+- Click the {{ icon("photo") }} button in the editor toolbar to select a file from your device
+- Paste an image directly from the clipboard
+- Drag and drop an image file into the editor
+
+Uploaded images are stored on the server and linked to the note. If a note is edited or deleted, any images that are no longer referenced by any note are automatically removed.
+
+## Adding a Note
+
+To add a note to an object:
+
+1. Navigate to the object's detail page
+2. Click on the **Notes** tab
+3. Click the **Add Note** button
+4. Fill in the `Title` (required) and optional `Description` fields
+5. Click **Submit**
+
+The new note will appear in the sidebar ready for editing.
+
+## Editing Note Content
+
+Note content is shown in read-only mode by default. To make changes:
+
+1. Click the {{ icon("pencil") }} icon in the note header to enter edit mode
+2. Use the toolbar to format content, insert images, or add tables
+3. Click the {{ icon("device-floppy") }} icon, or press **Ctrl+S** / **Cmd+S**, to save changes
+4. Click the {{ icon("check") }} icon to exit edit mode once all changes are saved
+
+!!! warning "Unsaved Changes"
+    If you navigate away from the Notes panel or leave the page while in edit mode with unsaved changes, InvenTree will prompt you to confirm before proceeding.
+
+### Resetting Changes
+
+While in edit mode, clicking the {{ icon("reload") }} icon discards any unsaved changes and reloads the last saved version of the note.
+
+## Editing Note Properties
+
+To change a note's title or description, open the actions menu in the note header and select **Edit Note**.
+
+## Deleting a Note
+
+To delete a note, open the actions menu in the note header and select **Delete Note**.
+
+!!! danger "Permanent Action"
+    Deleting a note is permanent and cannot be undone. Any images embedded in the note that are not referenced elsewhere will also be removed.
+
+## Note Templates
+
+Note templates are pre-defined notes that can be used as a starting point when adding a new note to any model instance. They allow administrators to standardize common note structures and reduce repetitive data entry.
+
+### Creating Notes from Templates
+
+When adding a new note to an object, an optional **From Template** field is available. Selecting a template pre-fills the **Title**, **Description**, and **Content** fields with the template's content. These fields can then be edited before saving.
+
+To create a note from a template:
+
+1. Navigate to the object's detail page and open the **Notes** tab
+2. Click the **Add Note** button
+3. In the **From Template** field, select an existing template from the dropdown
+4. The **Title**, **Description**, and **Content** fields are automatically populated from the template
+5. Edit any fields as needed
+6. Click **Submit** to save the note
+
+!!! info "Template Filters"
+    The template dropdown only shows templates that are applicable to the current model type, plus any templates that are not restricted to a specific model type.
+
+### Managing Note Templates
+
+Note templates are managed by staff users via the **Admin Center**.
+
+To access note templates:
+
+1. Navigate to **Settings** > **Admin Center**
+2. Select the **Note Templates** panel
+
+This panel provides the same rich-text editor interface used for regular notes. Templates created here are available to all users when adding notes across the system.
+
+#### Creating a Template
+
+1. In the **Note Templates** panel, click **Add Note Template**
+2. Enter a **Title** (required) and optional **Description**
+3. Optionally select a **Model Type** to restrict the template to a specific kind of object (e.g. *Part*, *Build Order*). Leave blank to make the template available for all model types
+4. Click **Submit**, then edit the template content in the editor
+
+#### Editing a Template
+
+Select a template from the sidebar, then use the same edit workflow as for regular notes: click the {{ icon("pencil") }} icon, make changes, and save with {{ icon("device-floppy") }} or **Ctrl+S** / **Cmd+S**.
+
+#### Deleting a Template
+
+Open the actions menu in the template header and select **Delete Note Template**.
+
+!!! note
+    Deleting a template does not affect any notes that were previously created from it.

docs/docs/manufacturing/build.md

@@ -211,9 +211,9 @@ Files attachments can be uploaded against the build order, and displayed in the
 
 ### Notes
 
-Build order notes (which support markdown formatting) are displayed in the *Notes* tab:
+One or more rich-text notes can be attached to a build order, and are displayed in the *Notes* tab.
 
-{{ image("build/build_notes.png", title="Notes") }}
+[Read about notes](../concepts/notes.md).
 
 ## External Build Orders
 

docs/docs/part/views.md

@@ -149,4 +149,6 @@ The *Part Attachments* tab displays file attachments associated with the selecte
 
 ### Notes
 
-A part may have notes attached, which support markdown formatting.
+A part may have one or more rich-text notes attached.
+
+[Read about notes](../concepts/notes.md).

docs/docs/plugins/develop.md

@@ -23,7 +23,7 @@ Consider the use-case for your plugin and define the exact function of the plugi
 - Do you need to run in the background ([ScheduleMixin](./mixins/schedule.md)) or when things in InvenTree change ([EventMixin](./mixins/event.md))?
 - Does the plugin need configuration that should be user changeable ([SettingsMixin](./mixins/settings.md)) or static (just use a yaml in the config dir)?
 - You want to receive webhooks? Do not code your own untested function, use the WebhookEndpoint model as a base and override the perform_action method.
-- Do you need the full power of Django with custom models and all the complexity that comes with that – welcome to the danger zone and [AppMixin](./mixins/app.md). The plugin will be treated as a app by django and can maybe rack the whole instance.
+- Do you need the full power of Django with custom models and all the complexity that comes with that - welcome to the danger zone and [AppMixin](./mixins/app.md). The plugin will be treated as a app by django and can maybe rack the whole instance.
 
 ### Define Metadata
 

docs/docs/report/helpers.md

@@ -979,9 +979,98 @@ Length: {{ length_value }}
 {% endraw %}
 ```
 
+## Notes
+
+[Notes](../concepts/notes.md) are rich-text documents that can be attached to most InvenTree model instances. Two template tags are available for accessing note content in a report.
+
+### note
+
+The `note` tag returns the rendered HTML content of a note, ready to embed directly in a report. Any images embedded in the note are automatically resolved to their base64-encoded data so that they appear in the generated PDF.
+
+::: report.templatetags.report.note
+    options:
+        show_docstring_description: false
+        show_source: False
+
+If no `title` argument is given, the [primary note](../concepts/notes.md#primary-note) is returned. If a `title` is given, the note whose title matches (case-insensitively) is returned instead. An empty string is returned when no matching note exists.
+
+#### Example
+
+```html
+{% raw %}
+{% load report %}
+
+<!-- Render the primary note for the part -->
+{% note part as part_note %}
+<div>{{ part_note }}</div>
+
+<!-- Render a note by title -->
+{% note part "Assembly Instructions" as instructions %}
+<div>{{ instructions }}</div>
+{% endraw %}
+```
+
+!!! info "Safe HTML Output"
+    The `note` tag returns pre-sanitized HTML and is marked safe for direct template rendering. Do **not** additionally wrap it with `| safe` or `| markdownify` — the content has already been processed.
+
+### note_instance
+
+The `note_instance` tag returns the `Note` object itself, giving access to its individual fields. This is useful when you need to display the note title, description, or metadata alongside its content.
+
+::: report.templatetags.report.note_instance
+    options:
+        show_docstring_description: false
+        show_source: False
+
+A `Note` object exposes the following attributes:
+
+| Attribute | Description |
+| --- | --- |
+| `title` | The title of the note |
+| `description` | An optional short description of the note |
+| `content` | The raw HTML content of the note |
+| `primary` | `True` if this is the primary note for the model instance |
+| `updated` | Timestamp of the last modification |
+| `updated_by` | The user who last modified the note |
+
+#### Example
+
+```html
+{% raw %}
+{% load report %}
+
+{% note_instance part as primary_note %}
+{% if primary_note %}
+<h3>{{ primary_note.title }}</h3>
+{% if primary_note.description %}<p><em>{{ primary_note.description }}</em></p>{% endif %}
+{% note part as note_content %}
+<div>{{ note_content }}</div>
+{% endif %}
+{% endraw %}
+```
+
+### Iterating Over All Notes
+
+When a model has multiple notes and you want to render all of them, access the `notes` queryset directly:
+
+```html
+{% raw %}
+{% load report %}
+
+{% for n in part.notes.all %}
+<h3>{{ n.title }}</h3>
+{% note part n.title as note_content %}
+<div>{{ note_content }}</div>
+{% endfor %}
+{% endraw %}
+```
+
 ## Rendering Markdown
 
-Some data fields (such as the *Notes* field available on many internal database models) support [markdown formatting](https://en.wikipedia.org/wiki/Markdown). To render markdown content in a custom report, there are template filters made available through the [django-markdownify](https://github.com/erwinmatijsen/django-markdownify) library. This library provides functionality for converting markdown content to HTML representation, allowing it to be then rendered to PDF by the InvenTree report generation pipeline.
+Some data fields (such as those provided by custom plugin models) may support [markdown formatting](https://en.wikipedia.org/wiki/Markdown). To render markdown content in a custom report, there are template filters made available through the [django-markdownify](https://github.com/erwinmatijsen/django-markdownify) library. This library provides functionality for converting markdown content to HTML representation, allowing it to be then rendered to PDF by the InvenTree report generation pipeline.
+
+!!! info "Notes"
+    [Notes](../concepts/notes.md) content is rich-text (stored as HTML) rather than markdown, and is already sanitized. Use the [note](#note) tag to render it - do not pass it through `markdownify`.
 
 To render markdown content in a report, consider the following simplified example:
 
@@ -990,9 +1079,9 @@ To render markdown content in a report, consider the following simplified exampl
 
 {% load markdownify %}
 
-<h3>Part Notes</h3>
+<h3>Description</h3>
 <p>
-    {{ part.notes | markdownify }}
+    {{ some_markdown_field | markdownify }}
 </p>
 {% endraw %}
 ```

docs/mkdocs.yml

@@ -107,6 +107,7 @@ nav:
     - Project Codes: concepts/project_codes.md
     - Attachments: concepts/attachments.md
     - Parameters: concepts/parameters.md
+    - Notes: concepts/notes.md
     - Tags: concepts/tags.md
     - Barcodes:
       - Barcode Support: barcodes/index.md

src/backend/InvenTree/InvenTree/api_version.py

@@ -1,11 +1,16 @@
 """InvenTree API version information."""
 
 # InvenTree API version
-INVENTREE_API_VERSION = 532
+INVENTREE_API_VERSION = 533
 """Increment this API version number whenever there is a significant change to the API that any clients need to know about."""
 
 INVENTREE_API_TEXT = """
 
+v533 -> 2026-08-16 : https://github.com/inventree/InvenTree/pull/11971
+    - Removes direct "notes" field from any models which previously supported markdown notes
+    - Adds a generic "Note" model which can be attached to any model type via a generic foreign key relationship
+    - Allow multiple notes to be attached to a single object, and for notes to be created / edited / deleted via the API
+
 v532 -> 2026-08-15 : https://github.com/inventree/InvenTree/pull/12422
     - Adds "piece_count" field to the BomItem model and API endpoints (for cut-to-length parts)
 
@@ -49,7 +54,7 @@
     - Adds new "disassemble" API endpoint for stock items
     - Allows a stock item to be broken down into component parts, based on its Bill of Materials
 
-v519 -> 2026-07-09 : https://github.com/inventree/InvenTree/pull/TODO
+v519 -> 2026-07-09 : https://github.com/inventree/InvenTree/pull/12334
     - Adds optional "roles" and "permissions" fields to the /user/me/ API endpoint, via the "?roles=true" query parameter
 
 v518 -> 2026-07-09 : https://github.com/inventree/InvenTree/pull/12341

src/backend/InvenTree/InvenTree/apps.py

@@ -100,11 +100,11 @@ def ready(self):
     def remove_obsolete_tasks(self):
         """Delete any obsolete scheduled tasks in the database."""
         obsolete = [
+            'data_exporter.tasks.cleanup_old_export_outputs',
             'InvenTree.tasks.delete_expired_sessions',
-            'stock.tasks.delete_old_stock_items',
             'label.tasks.cleanup_old_label_outputs',
             'report.tasks.cleanup_old_report_outputs',
-            'data_exporter.tasks.cleanup_old_export_outputs',
+            'stock.tasks.delete_old_stock_items',
         ]
 
         try: