d102593c0a
* add consideration to templates * use emoji for better visibility * fix: always run CodeQL --------- Co-authored-by: Alain Nicolas <alain.nicolas@consensys.net>
1.1 KiB
name, about, title, labels, assignees
| name | about | title | labels | assignees |
|---|---|---|---|---|
| Bug report | File a bug report | Short and factual title summarizing the bug. | Bug |
🔐 🔐 Should this be a security advisory instead? 🔐 🔐
Remenber not to put too much unhelpful information or too little important information, be specific.
Impact
environment [Testnet/Mainnet]
an user is impacted [Y/N], if yes type of user: [External/Internal]
Describe the bug
Steps to Reproduce
A bug that we can't reproduce is hard to resolve, to ensure the bug is fixed in a timely manner, it is crucial to indicate how to reproduce it. If the bug can't be reproduced, give specific details on how it happened.
Steps to reproduce the bug:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Actual result
Evidence of the bug including log extracts, screen shot, wallet addresses, Tx hash, ...
Expected result
A clear and concise description of what you expected to happen.
Remember that an issue without proper labels and without assignee is unlikely to get prioritized -> contact the team or the product owner to get it included in the plan.