You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**DO NOT OPEN AN ISSUE FOR GENERAL SUPPORT QUESTIONS.**
22
+
23
+
options:
24
+
- label: Yes, I have searched for similar issues on [GitHub](https://github.com/EvolutionAPI/evolution-api/issues) and found none.
25
+
required: true
26
+
27
+
- type: textarea
28
+
attributes:
29
+
label: What did you do?
30
+
description: |
31
+
How to write a good bug report?
32
+
33
+
- Respect the issue template as much as possible.
34
+
- The title should be short and descriptive.
35
+
- Explain the conditions that led you to report this issue: the context.
36
+
- The context should lead to something, an idea or problem you are facing.
37
+
- Be clear and concise.
38
+
- Format your messages to help the reader focus on what matters and understand the structure of your message, use [Markdown syntax](https://help.github.com/articles/github-flavored-markdown)
39
+
placeholder: Describe the problem you encountered in detail.
40
+
validations:
41
+
required: true
42
+
43
+
- type: textarea
44
+
attributes:
45
+
label: What did you expect?
46
+
placeholder: Describe what you expected to happen.
47
+
validations:
48
+
required: true
49
+
50
+
- type: textarea
51
+
attributes:
52
+
label: What did you observe instead of what you expected?
53
+
placeholder: Explain what actually happens when you follow the steps above.
54
+
validations:
55
+
required: true
56
+
57
+
- type: textarea
58
+
attributes:
59
+
label: Screenshots/Videos
60
+
placeholder: |
61
+
If possible, add screenshots or videos that illustrate the problem. This can be extremely helpful in understanding the issue better.
62
+
63
+
- type: textarea
64
+
attributes:
65
+
label: Which version of the API are you using?
66
+
description: |
67
+
Enter the version number found in the `version` property of the **package.json**.
description: '**DO NOT OPEN FOR GENERAL SUPPORT QUESTIONS.**'
14
+
15
+
options:
16
+
- label: Yes, I have searched for similar requests on [GitHub](https://github.com/code-chat-br/whatsapp-api/issues) and found none.
17
+
required: true
18
+
19
+
- type: dropdown
20
+
attributes:
21
+
label: What type of feature?
22
+
description: |
23
+
How to write a good feature request?
24
+
25
+
- Respect the issue template as much as possible.
26
+
- The title should be short and descriptive.
27
+
- Explain the conditions that led you to suggest this feature: the context.
28
+
- The context should lead to something, an idea or problem you are facing.
29
+
- Be clear and concise.
30
+
- Format your messages to help the reader focus on what matters and understand the structure of your message, use [Markdown syntax](https://help.github.com/articles/github-flavored-markdown)
31
+
options:
32
+
- Integration
33
+
- Functionality
34
+
- Endpoint
35
+
- Database adjustment
36
+
- Other
37
+
validations:
38
+
required: true
39
+
40
+
- type: textarea
41
+
attributes:
42
+
label: What is the motivation for the request?
43
+
description: |
44
+
What problem does the feature seek to solve?
45
+
Clearly and in detail describe the functionality you want to be implemented.
46
+
Explain how it fits into the context of the project.
47
+
placeholder: Detailed description
48
+
validations:
49
+
required: true
50
+
51
+
- type: textarea
52
+
attributes:
53
+
label: Usage Examples
54
+
description: |
55
+
Provide specific examples of how this functionality could be used.
56
+
This can include scenarios or use cases where the feature would be particularly beneficial.
57
+
placeholder: text - image - video - flowcharts
58
+
validations:
59
+
required: false
60
+
61
+
- type: textarea
62
+
attributes:
63
+
label: How should the feature be developed?
64
+
description: |
65
+
Should it be inserted directly into the code?
66
+
Should it be built as a different application that acts as an extension of the API?
67
+
For example: a `worker`?
68
+
69
+
Discuss how this new functionality could impact other parts of the project, if applicable.
70
+
71
+
---
72
+
73
+
If you have ideas on how this functionality could be implemented, please share them here.
74
+
This is not mandatory, but it can be helpful for the development team.
75
+
76
+
placeholder: Insert feature ideas here
77
+
validations:
78
+
required: false
79
+
80
+
- type: textarea
81
+
attributes:
82
+
label: Additional Notes
83
+
description: Any other information you believe is relevant to your request.
description: Crie um relatório para nos ajudar a melhorar.
3
+
labels:
4
+
- bug
5
+
- pt-br
6
+
# - help wanted
7
+
# Atrubuir automaticamente a issue a:
8
+
# assignees: DavidsonGomes
9
+
body:
10
+
- type: checkboxes
11
+
id: termos
12
+
attributes:
13
+
label: Bem-vido!
14
+
description: |
15
+
O rastreador de problemas é apenas para relatar bugs e solicitações de recursos.
16
+
Para perguntas de suporte relacionadas ao usuário final, acesse:
17
+
- [Discord](https://evolution-api.com/discord)
18
+
- [Grupo do WhatsApp](https://evolution-api.com/whatsapp)
19
+
<br/>
20
+
21
+
**NÃO ABRA UM PROBLEMA PARA PERGUNTAS GERAIS DE SUPORTE.**
22
+
23
+
options:
24
+
- label: Sim, pesquisei problemas semelhantes no [GitHub](https://github.com/EvolutionAPI/evolution-api/issues) e não encontrei nenhum.
25
+
required: true
26
+
27
+
- type: textarea
28
+
attributes:
29
+
label: O que você fez?
30
+
description: |
31
+
Como escrever um bom relatório de bug?
32
+
33
+
- Respeite o modelo de problema tanto quanto possível.
34
+
- O título deve ser curto e descritivo.
35
+
- Explique as condições que o levaram a reportar este problema: o contexto.
36
+
- O contexto deve levar a algo, ideia ou problema que você está enfrentando.
37
+
- Seja claro e conciso.
38
+
- Formate suas mensagens para ajudar o leitor a se concentrar no que importa e entender a estrutura da sua mensagem, use [sintaxe Markdown](https://help.github.com/articles/github-flavored-markdown)
39
+
placeholder: Descreva detalhadamente o problema que você encontrou.
40
+
validations:
41
+
required: true
42
+
43
+
- type: textarea
44
+
attributes:
45
+
label: O que você esperava?
46
+
placeholder: Descreva o que você esperava que acontecesse.
47
+
validations:
48
+
required: true
49
+
50
+
- type: textarea
51
+
attributes:
52
+
label: O que vc observou ao invés do que esperava?
53
+
placeholder: Explique o que realmente acontece quando você segue os passos acima.
54
+
validations:
55
+
required: true
56
+
57
+
- type: textarea
58
+
attributes:
59
+
label: Capturas de Tela/Vídeos
60
+
placeholder: |
61
+
Se possível, adicione capturas de tela ou vídeos que ilustrem o problema. Isso pode ser extremamente útil para entender melhor o problema.
62
+
63
+
- type: textarea
64
+
attributes:
65
+
label: Qual versão da API você está usando?
66
+
description: |
67
+
Insira o número da sua versão que está na propriedade `version` do **package.json**.
68
+
placeholder: Cole aqui a versão.
69
+
validations:
70
+
required: true
71
+
72
+
- type: dropdown
73
+
id: select
74
+
attributes:
75
+
label: Qual é o seu ambiente?
76
+
options:
77
+
- Windows
78
+
- Linux
79
+
- Mac
80
+
- Docker
81
+
- Outro
82
+
validations:
83
+
required: true
84
+
85
+
- type: textarea
86
+
attributes:
87
+
label: Outras expecificações do ambiente
88
+
placeholder: 'Hardware/Software: [ex: CPU, GPU]'
89
+
validations:
90
+
required: false
91
+
92
+
- type: textarea
93
+
attributes:
94
+
label: Se aplicável, cole a saída do log
95
+
description: |
96
+
Por favor, anexe os logs que possam estar relacionados ao problema.
97
+
Se os logs contiverem informações sensíveis, considere enviá-los de forma privada para um dos mantenedores do projeto.
98
+
placeholder: Cole aqui o log da aplicação
99
+
validations:
100
+
required: false
101
+
102
+
- type: textarea
103
+
attributes:
104
+
label: Notas Adicionais
105
+
description: Inclua aqui qualquer outra informação que você ache que possa ser útil para entender ou resolver o bug.
0 commit comments