37 lines
1.1 KiB
Markdown
37 lines
1.1 KiB
Markdown
---
|
||
name: Feature request
|
||
about: Suggest an idea for this project
|
||
|
||
---
|
||
|
||
<!--
|
||
DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS.
|
||
|
||
The issue tracker is for reporting bugs and feature requests only.
|
||
For end-user related support questions, please refer to one of the following:
|
||
|
||
- Stack Overflow (using the "traefik" tag): https://stackoverflow.com/questions/tagged/traefik
|
||
- the Traefik community Slack channel: https://slack.traefik.io
|
||
|
||
-->
|
||
|
||
|
||
### Do you want to request a *feature* or report a *bug*?
|
||
|
||
Feature
|
||
|
||
### What did you expect to see?
|
||
|
||
<!--
|
||
|
||
HOW TO WRITE A GOOD ISSUE?
|
||
|
||
- Respect the issue template as much as possible.
|
||
- The title should be short and descriptive.
|
||
- Explain the conditions which led you to report this issue: the context.
|
||
- The context should lead to something, an idea or a problem that you’re facing.
|
||
- Remain clear and concise.
|
||
- 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
|
||
|
||
-->
|