Team: Pranav Pandey Abhinav Goel

[Audio] Welcome to Insight Genie Hackathon Idea Presentation. Team members worked on this idea are - Abhinav Goel and Pranav Pandey.

[Audio] In our organization, diverse PR/ER/IR tools are utilized for reporting and managing issues. However, common problems arise such as duplicate PRs, misassigned PRs, issues that actually function as designed, and duplicates reported by different customers, stake holder, and users. This leads to inefficiencies, redundant efforts, and delays in issue resolution. Persistently logged actions in the PR database can be leveraged to streamline these processes. InsightGenie aims to address these challenges by utilizing AI to suggest potential duplicates, appropriate functional areas, correct functional owners, and relevant historical data during PR filing and review. By providing timely suggestions and insights, InsightGenie can help avoid duplicate efforts, ensure accurate PR assignment, recognize enhancement requests, and assist developers with proven resolution steps. This not only increases overall efficiency but also minimizes wasted resources and provides a clearer picture of reported issues..

Audio] An issue has been identified by the development or quality assurance team or Issue can be found by customer, services or pre-sales team. G TAC Gathers information from customer and Validate reported scenarios. G TAC Refer to the FAQ and help documentation to understand the issue better. And then Check for any similar existing issues that have been reported previously. Based on the investigation, G TAC decides whether to create a P R I R or resolve or reject the issue. The process of creating or rejecting a incident takes approximately 2 to 4 hours for G TAC. Developer one Collects all relevant information and validate the scenario described in the issue and Conduct a thorough investigation to understand the root cause of the issue. If needed consult the experts, product manager, or product owner. Then Document all findings in the P R Dev scratchpad for future reference. P R either Assign to the appropriate team or owner for further handling. Or Implement a fix to resolve the identified functional issue. If P R is reassigned then developer 2 also follows the same set of process to fix the issue. The process of resolving a issue completely takes approximately around 16 to 20 hours for a developer. Once the P R is resolved, database with the latest information is updated..