# What happens when bugs are caught in production?

**URL:** <https://club.ministryoftesting.com/t/what-happens-when-bugs-are-caught-in-production/28905>\
**Category:** Archive\
**Tags:** process\
**Created:** [9 September 2019 07:34 UTC](https://club.ministryoftesting.com/t/what-happens-when-bugs-are-caught-in-production/28905 "2019-09-09T07:34:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rosie](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/rosie/32/7719_2.png) [@rosie](https://club.ministryoftesting.com/u/rosie)\
**Post date:** [9 September 2019 07:34 UTC](https://club.ministryoftesting.com/t/what-happens-when-bugs-are-caught-in-production/28905/1 "2019-09-09T07:34:09Z")

</div>

What happens in you project context when a bug is caught in production?

What kind of things, in your opinion, shouldn’t happen?

What kind of things, in your opinion, should happen?

_[LinkedIn](https://www.linkedin.com/feed/update/urn:li:activity:6576724618059612160) and [Twitter](https://twitter.com/ministryoftest/status/1170962410494185472) versions for fun too. 🙂_

---

<div class="post-metadata">

**Author:** ![chris\_dabnor](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/chris_dabnor/32/6251_2.png) [@chris\_dabnor](https://club.ministryoftesting.com/u/chris_dabnor)\
**Post date:** [9 September 2019 07:49 UTC](https://club.ministryoftesting.com/t/what-happens-when-bugs-are-caught-in-production/28905/2 "2019-09-09T07:49:40Z")

</div>

Attempt to reproduce it. Write out the steps to reproduce. Friendly devs fix it. Test it. Support inform everyone who experienced it. Get everyone involved together for a post mortem meeting (5 whys etc). If deemed necessary, write a formal post mortem. For me, one of the most important parts of it all is to stop people feeling guilty, or stressed, or in any way bad about it. A post mortem is a learning document.

---

<div class="post-metadata">

**Author:** ![conrad.braam](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/conrad.braam/32/660_2.png) [@conrad.braam](https://club.ministryoftesting.com/u/conrad.braam)\
**Post date:** [11 September 2019 13:27 UTC](https://club.ministryoftesting.com/t/what-happens-when-bugs-are-caught-in-production/28905/3 "2019-09-11T13:27:16Z")

</div>

panic…  
Read the customer ticket, and Inform the parties that need to know soonest.  
Don’t : Spend loads of time trying to repro the problem, you don’t own the defect, the team does.  
Do : Try and understand how the defect arose for yourself as a tester, go learn more about the environment and the use-case that caused the unhappy customer. Place the defect in a context, and then scan the vicinity for similar animals hiding around the same spot. Finding and Dealing with these at the same time may save time now.

---

<div class="post-metadata">

**Author:** ![bathiya](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/bathiya/32/6148_2.png) [@bathiya](https://club.ministryoftesting.com/u/bathiya)\
**Post date:** [11 September 2019 13:58 UTC](https://club.ministryoftesting.com/t/what-happens-when-bugs-are-caught-in-production/28905/4 "2019-09-11T13:58:01Z")

</div>

its painful sometimes 🙂  
first we check the priority, if the bug is critical/blocker first thing we do is plan a hot fix to roll-out . at this situation no point of trying to find how this happened if its clear what need to do to fix the customer problems.  
then do a further analysis to understand what went wrong.