---
title: "Introduction"
manual: "Context Reporter"
version: "main"
permalink: "https://docs.typo3.org/permalink/priebera/typo3-context-reporter:introduction@main"
source: "Introduction/Index.rst"
rendered: "2026-09-23T13:31:15+00:00"
---

# Introduction {#introduction}

## What does it do? {#introduction-what}

When an editor notices a problem in the TYPO3 backend, the hardest part for
the support team is usually to find out *where* it happened. Context Reporter
answers this question automatically:

```text
problem → reporter → structured report → download / email / webhook → external system
```

An editor can start a report where the object is:

-   the **Report a problem** button in the backend toolbar,
-   the report action of a row in **Web > List**,
-   the report action in the document header of **Web > Page**,
-   the report action of a file or folder in the list view of
    **File > Filelist**,
-   **Report a problem with this page**,
    **Report a problem with this record**,
    **Report a problem with this file** or
    **Report a problem with this folder** in the context menu,
-   the **Report problem** button in the document header of the record
    editing form.

All entry points use the same speech bubble icon.

The report dialog shows the detected object as a compact card, for example
**Page Content · Text & Media**, **Our story**,
`tt_content:2 · About us` and `main · English · Live · Web › List`. It asks
for a short title and an optional description and screenshot, and shows all
technical data that will be sent.

![The report dialog with the detected content element "Our story", its page, site, language, workspace and module, a title, a description and an annotated screenshot with a redacted area](../Images/context-reporter-dialog.png)

## Collected context {#introduction-context}

-   **Subject**

    The page, record, file, folder or backend view the report is about, with
    its label, type and a backend link.

-   **Page**

    UID, PID, title, slug, page type, hidden flag, rootline, backend link,
    edit link and frontend URL.

-   **Record**

    Table, UID, PID, label, record type with its label, language,
    translation source, `colPos`, hidden flag, workspace version and backend
    link. Apart from the label (the title TYPO3 shows for the record), no
    field values are collected; multi-line text such as the body text of a
    content element is never used as label.

-   **File**

    `sys_file` UID, storage UID, identifier, name, extension, MIME type,
    size, missing flag, metadata UID, and links to the file list and the
    metadata record. File contents and metadata values are not collected.

-   **Folder**

    Storage UID, identifier, name and a file list link. Reports about a file
    include its folder.

-   **Storage**

    UID, name, driver type, whether it is public and whether it is offline.
    The storage configuration is not collected.

-   **Editing form**

    Edited records, defaults of a new record (type, language and `colPos`
    only) and restricted fields.

-   **Site, language, workspace**

    Site identifier, base and root page; language ID, title and locale;
    workspace ID and title.

-   **Backend**

    Module, route and backend language. Tokens and return URLs are removed.

-   **System**

    TYPO3 and PHP versions, application context, Composer mode, database
    platform, operating system and extension version.

-   **Browser**

    Browser, operating system, user agent, languages, time zone, window and
    screen size, pixel ratio, color scheme and reduced motion preference (can
    be disabled).

-   **Reporter**

    UID and username by default. Real name, email address and groups are
    opt-in.

-   **Recent backend errors**

    Opt-in: the reporter's own error and warning entries of the backend log,
    see [Recent backend errors](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:privacy-recent-errors@main).

The report dialog shows all of this before the report is sent. See
[Privacy and security](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:privacy-security@main) for what is deliberately not collected.

## What it is not {#introduction-scope}

Context Reporter is intentionally not a ticket system. It has no boards,
workflows, assignments, priorities, comments, due dates, SLAs or time
tracking, and no native Jira, GitLab, GitHub or Slack connectors. The local
**Context Reports** module is an audit log with manual retry, copy
and download actions, and a simple [open/resolved marker](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:usage-review@main).
Use the [webhook](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:integration-webhook@main) to connect any other system.

All features are part of the extension. There is no paid edition that unlocks
functionality.