a20469f038
* rename float to discrete
* use same section title level on all source files
* Elasticsearch => {es}
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
46 lines
1.8 KiB
Plaintext
46 lines
1.8 KiB
Plaintext
[[kibana-issue-reporting]]
|
||
== Effective issue reporting in {kib}
|
||
|
||
[discrete]
|
||
=== Voicing the importance of an issue
|
||
|
||
We seriously appreciate thoughtful comments. If an issue is important to
|
||
you, add a comment with a solid write up of your use case and explain
|
||
why it’s so important. Please avoid posting comments comprised solely of
|
||
a thumbs up emoji 👍.
|
||
|
||
Granted that you share your thoughts, we might even be able to come up
|
||
with creative solutions to your specific problem. If everything you’d
|
||
like to say has already been brought up but you’d still like to add a
|
||
token of support, feel free to add a
|
||
https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments[👍
|
||
thumbs up reaction] on the issue itself and on the comment which best
|
||
summarizes your thoughts.
|
||
|
||
[discrete]
|
||
=== "`My issue isn’t getting enough attention`"
|
||
|
||
First of all, *sorry about that!* We want you to have a great time with
|
||
{kib}.
|
||
|
||
There’s hundreds of open issues and prioritizing what to work on is an
|
||
important aspect of our daily jobs. We prioritize issues according to
|
||
impact and difficulty, so some issues can be neglected while we work on
|
||
more pressing issues.
|
||
|
||
Feel free to bump your issues if you think they’ve been neglected for a
|
||
prolonged period.
|
||
|
||
[discrete]
|
||
=== "`I want to help!`"
|
||
|
||
*Now we’re talking*. If you have a bug fix or new feature that you would
|
||
like to contribute to {kib}, please *find or open an issue about it
|
||
before you start working on it.* Talk about what you would like to do.
|
||
It may be that somebody is already working on it, or that there are
|
||
particular issues that you should know about before implementing the
|
||
change.
|
||
|
||
We enjoy working with contributors to get their code accepted. There are
|
||
many approaches to fixing a problem and it is important to find the best
|
||
approach before writing too much code. |