This article is also available in:
A collaborative solution

Fabriq was designed to help teams better address issues and collaborate. Therefore, when creating a ticket it is important to be as comprehensive as possible to allow others who will be working with the ticket to be as informed as possible.

To do this, make sure you provide as many details as possible when creating the ticket, for example:

Title: Try to use an accurate title. It will be more judicious to use Oil leak at the RJ45 machine than Oil leak for example.

Description: Describe the problem correctly and think of your colleague who will read you later.

Original team: Indicate the team that issued the ticket. It will not be possible to change the original team afterwards.

Category*: Indicate the category that is most relevant to the problem you are describing.

Indicators: If you think it is relevant, feel free to link an indicator to the ticket, this will allow you to directly track the problems related to a particular indicator.

Task: If you can, indicate immediately the tasks to be taken to solve the problem. You can do this as soon as you create a ticket.

Root cause: If you know the source of the problem, indicate it, it will be useful for everyone afterwards. Sometimes this is not possible and identifying the root cause will require going through longer processes such as the 5 Whys method or a more general audit.

Other team: If you want to share the ticket with another team to escalate the problem or get help from support, this is the place to do it.

Label: The label allows you to specify if a problem is urgent, for example.

Attachment: Illustrate the problem with a photo of the field for example.
Was this article helpful?
Thank you!