# Should I feel guilty about opening bug reports?

**URL:** https://meta.discourse.org/t/should-i-feel-guilty-about-opening-bug-reports/39359
**Category:** Site feedback
**Created:** [2월 10, 2016, 7:37오후 UTC](https://meta.discourse.org/t/should-i-feel-guilty-about-opening-bug-reports/39359 "2016-02-10T19:37:24Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Alankrit\_Choudh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/alankrit_choudh/32/119698_2.png) [@Alankrit\_Choudh](https://meta.discourse.org/u/Alankrit_Choudh)
#### Post date: [2월 10, 2016, 7:37오후 UTC](https://meta.discourse.org/t/should-i-feel-guilty-about-opening-bug-reports/39359/1 "2016-02-10T19:37:24Z")

</div>

Solving a bug is work, _it is hard work_. Lately have been posting few bugs on meta here, and i am feeling guilty about it doing so, because its like adding more problems to a problem.  
I really hope the bugs which i post make sense and are actually bugs.

 ![](https://global.discourse-cdn.com/meta/original/3X/6/0/601c6369cf55c81add8c5598e6f31d9c3781532b.gif)

---

<div class="post-metadata">

### Author: ![downey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/downey/32/166878_2.png) [@downey](https://meta.discourse.org/u/downey)
#### Post date: [2월 10, 2016, 7:41오후 UTC](https://meta.discourse.org/t/should-i-feel-guilty-about-opening-bug-reports/39359/2 "2016-02-10T19:41:06Z")

</div>

Never feel guilty about finding & reporting bugs. That’s how free & open source software like Discourse gets better!

🏆 ⭐

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2월 10, 2016, 8:08오후 UTC](https://meta.discourse.org/t/should-i-feel-guilty-about-opening-bug-reports/39359/3 "2016-02-10T20:08:59Z")

</div>

As long as they are

1. Reproducible on try & meta
2. Contain a clear, complete set of repro steps
3. Actually **prevent normal use of Discourse** as described in the bug category description

That’s fine..

---

<div class="post-metadata">

### Author: ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [2월 11, 2016, 12:46오전 UTC](https://meta.discourse.org/t/should-i-feel-guilty-about-opening-bug-reports/39359/4 "2016-02-11T00:46:59Z")

</div>

> [@codinghorror](#):
>
> Reproducible on try & meta

@codinghorror, I generally do not test bugs on both try **and** Meta. I tend to assume if it doesn’t work on Meta (and there isn’t an experiment going on like a new post renderer) then I am safe to report it. Should I be checking all bugs found on my instance on both sites before reporting?

---

<div class="post-metadata">

### Author: ![featheredtoast](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/featheredtoast/32/116994_2.png) [@featheredtoast](https://meta.discourse.org/u/featheredtoast)
#### Post date: [2월 11, 2016, 1:02오전 UTC](https://meta.discourse.org/t/should-i-feel-guilty-about-opening-bug-reports/39359/5 "2016-02-11T01:02:03Z")

</div>

I’d say it’s better to have the discussion about whether or not a bug is valid than the alternative…

 ![](https://global.discourse-cdn.com/meta/original/4X/c/a/1/ca16038c1189ebfcfdb00f568f34a4dc42d97b5b.png)  
I must say that despite the influx of bug reports, the team has been doing an excellent job managing them so quickly!

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2월 11, 2016, 1:10오전 UTC](https://meta.discourse.org/t/should-i-feel-guilty-about-opening-bug-reports/39359/6 "2016-02-11T01:10:27Z")

</div>

It is an issue at the moment since meta is on the vdom branch. That’s why I mentioned it.