Skip to content

Better description of how to troubleshoot and reporting errors due diligence #1849

Open
@oesteban

Description

@oesteban

With the increase in users, the feedback we receive is also more unclear. Most of our support interactions start with some general guidelines to find out the exact cause of problems and paths where the user can find further information.

Perhaps we could create this documentation based on GitHub's issue template.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions