I am working on large scale platform, There are several applications combined into one solution. My team ( I am one of them) runs/tests use cases on that overall platform(Solution). Two of the application are not stable at all, one day they work fine and other day they don't. How to deal in this kind of situation. I am new to this solution and i am still struggling to understand the system. There will be bunch of emails every day. I am very confused to keep rack of them.
How do you guys deal with this kind of situation. Suggestions from seniors
Are you using a bug tracking system? If not, you should. That could help avoid the clutter of emails that you have trouble tracking.
Are the stability changes happening due to new builds of the application or system? That is, does it work fine in one build and then fail in another? If so, you may consider a Smoke Test where you reject a build which fails the Smoke Test. Some shops require developers to stop what they are doing and immediately fix the problem when their build fails a Smoke Test.
If the issue is tracking all the correspondance then create a log of issues. It sounds like there is not a common bug reporting tool as this would be the logical place to put all this information. Creating a log and circulating can then create a focus for disussion and make it easier for everyone as they don't also have to wade through heaps of email.
I've found myself doing similar things when getting user feedback from UATs as a way to make sure my team had responded to all reported issues.
The story so far:
In the beginning the Universe was created.
This has made a lot of people very angry and been widely regarded as a bad move.