Hi @Anjana Shrivastava,
I am sure you are aware that this is not a simple ask, that will not be solved by a template or one or two quick actions, right ...
If you suddenly see spikes in the number of issues being reported for a product, you can quite confidently make an educated guess that something has changed. A big release, a small fix that has broken an integration, a critical service being done, ...
If it happens frequently that stuff breaks after a new release, there's a strong indication that something is not entirely right with code quality, your development, testing and/or release processes or maybe even the underlying architecture. What you can and/or should do to fix that requires a holistic approach of all that and is very much depending on how you work, how your code base evolved over time and how mature your people, processes and tools currently are.
As a pointer towards better insights for root cause analysis: Jira Service Management allows you to connect your CI/CD tools to your service desk, so you can pull in development information into your service desk tools. When an incident occurs for a service, the incident investigation feature allows you to display the deployments that have recently happend right from the incident ticket.
For more tips, you may want to check out this best practice and tips guide
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.