mirror of
https://github.com/apache/superset.git
synced 2024-09-12 08:39:45 -04:00
50 lines
1.2 KiB
Markdown
50 lines
1.2 KiB
Markdown
---
|
|
name: Bug report
|
|
about: "Create a report to help us improve Superset's stability! For feature requests please open a discussion [here](https://github.com/apache/superset/discussions/categories/ideas)."
|
|
labels: bug
|
|
---
|
|
|
|
A clear and concise description of what the bug is.
|
|
|
|
#### How to reproduce the bug
|
|
|
|
1. Go to '...'
|
|
2. Click on '....'
|
|
3. Scroll down to '....'
|
|
4. See error
|
|
|
|
### Expected results
|
|
|
|
what you expected to happen.
|
|
|
|
### Actual results
|
|
|
|
what actually happens.
|
|
|
|
#### Screenshots
|
|
|
|
If applicable, add screenshots to help explain your problem.
|
|
|
|
|
|
### Environment
|
|
|
|
(please complete the following information):
|
|
|
|
- browser type and version:
|
|
- superset version: `superset version`
|
|
- python version: `python --version`
|
|
- node.js version: `node -v`
|
|
- any feature flags active:
|
|
|
|
### Checklist
|
|
|
|
Make sure to follow these steps before submitting your issue - thank you!
|
|
|
|
- [ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
|
|
- [ ] I have reproduced the issue with at least the latest released version of superset.
|
|
- [ ] I have checked the issue tracker for the same issue and I haven't found one similar.
|
|
|
|
### Additional context
|
|
|
|
Add any other context about the problem here.
|