# Jira Backlog Report - 2026-03-15

Total Stories: 62

## Summary Table

| Key | Summary | Status | Assignee | Priority |
| --- | --- | --- | --- | --- |
| [DEB-379](https://divami.atlassian.net/browse/DEB-379) | Training and Learning Lifecycle | Start | Rajashekar Gummadidala | Medium |
| [DEB-378](https://divami.atlassian.net/browse/DEB-378) | Refresh Insights and Escalation Lifecycle | Start | Rajashekar Gummadidala | Medium |
| [DEB-377](https://divami.atlassian.net/browse/DEB-377) | Refresh Agent Lifecycle | Start | Rajashekar Gummadidala | Medium |
| [DEB-370](https://divami.atlassian.net/browse/DEB-370) | Training Lifecycle | Start | Rajashekar Gummadidala | Medium |
| [DEB-366](https://divami.atlassian.net/browse/DEB-366) | Alert Lifecycle (Agent to understand Escallations) | Start | Maggidi Amulya | Medium |
| [DEB-364](https://divami.atlassian.net/browse/DEB-364) | Data Source Agent: REST API Adaptor | Start | Rajashekar Gummadidala | Medium |
| [DEB-362](https://divami.atlassian.net/browse/DEB-362) | Data Source Agent: Adhoc Query Lifecycle - II | Start | arpit | Medium |
| [DEB-360](https://divami.atlassian.net/browse/DEB-360) | Data Source Agent: Adhoc Query Lifecycle - I | Start | Rahul Mishra | Medium |
| [DEB-353](https://divami.atlassian.net/browse/DEB-353) | Alert Lifecycle - Backend | Start | kalakondaHarshithRao | Medium |
| [DEB-348](https://divami.atlassian.net/browse/DEB-348) | Training Lifecycle | Start | Rajashekar Gummadidala | Medium |
| [DEB-344](https://divami.atlassian.net/browse/DEB-344) | Core: Knowledge Base Setup and CRUD operations on Knowledge Base for Org Snapshot & Knowledge Graph | Start | Phawhan Saii Gajjalakonda | Medium |
| [DEB-340](https://divami.atlassian.net/browse/DEB-340) | Core: Knowledge Base Setup and CRUD operations on Knowledge Base for Org Info | Start | Abhilash Adunuri | Medium |
| [DEB-327](https://divami.atlassian.net/browse/DEB-327) | Adhoc Question and Answer Lifecycle - I | Start | Yeshwanth Reddy Yerraguntla | Medium |
| [DEB-322](https://divami.atlassian.net/browse/DEB-322) | Context Propagation Lifecycle | Start | Yeshwanth Reddy Yerraguntla | Medium |
| [DEB-317](https://divami.atlassian.net/browse/DEB-317) | Implement Backend Authentication APIs (Google OAuth & Username/Password) | Start | Manisha Gundapuneedi | Medium |
| [DEB-313](https://divami.atlassian.net/browse/DEB-313) | Implement Login UI with Feature Flag Support | Start | Manisha Gundapuneedi | Medium |
| [DEB-312](https://divami.atlassian.net/browse/DEB-312) | Feature Flag implementation for Login type (SSO or Basic Auth) | Start | Unassigned | Medium |
| [DEB-311](https://divami.atlassian.net/browse/DEB-311) | Finalize UI Architecture and Visualization Libraries | Start | Unassigned | Medium |
| [DEB-308](https://divami.atlassian.net/browse/DEB-308) | Evaluate CopilotKit for Dashboard and Chat Integration | Start | saianitha | Medium |
| [DEB-307](https://divami.atlassian.net/browse/DEB-307) | Simulator POC | Start | Ganesh Danuri | Medium |
| [DEB-306](https://divami.atlassian.net/browse/DEB-306) | ? | Start | Unassigned | Medium |
| [DEB-305](https://divami.atlassian.net/browse/DEB-305) | 0. Create LLD Document and get approval | Start | Unassigned | Medium |
| [DEB-304](https://divami.atlassian.net/browse/DEB-304) | 0. Create LLD Document and get approval | Start | Unassigned | Medium |
| [DEB-303](https://divami.atlassian.net/browse/DEB-303) | Demo Support | Start | Unassigned | Medium |
| [DEB-246](https://divami.atlassian.net/browse/DEB-246) | test | Start | Unassigned | Medium |
| [DEB-244](https://divami.atlassian.net/browse/DEB-244) | test | Open | Unassigned | Medium |
| [DEB-243](https://divami.atlassian.net/browse/DEB-243) | Core Agent Architecture | Start | Unassigned | Medium |
| [DEB-242](https://divami.atlassian.net/browse/DEB-242) | Oracle Unifier Architecture | Start | Manisha Gundapuneedi | Medium |
| [DEB-205](https://divami.atlassian.net/browse/DEB-205) | Enterprise Brain UI | Development in Progress | kalakondaHarshithRao | Medium |
| [DEB-204](https://divami.atlassian.net/browse/DEB-204) | Sources identification along with the resposne by agent | Development in Progress | Maggidi Amulya | Medium |
| [DEB-203](https://divami.atlassian.net/browse/DEB-203) | Query validation layer to validate the queries generated by the agent | Start | Unassigned | Medium |
| [DEB-145](https://divami.atlassian.net/browse/DEB-145) | Implementation of Personalisation of the application to individuals | Start | Maggidi Amulya | Medium |
| [DEB-144](https://divami.atlassian.net/browse/DEB-144) | Building the actual simulator that will have the canvas to render the dynamic ineteractive dashboards with AI intelligence | Start | Rajashekar Gummadidala | Medium |
| [DEB-143](https://divami.atlassian.net/browse/DEB-143) | Implementation of Intelligent Dynamic and Interactive Dashboard Simulator | Development in Progress | Rahul Mishra | Medium |
| [DEB-140](https://divami.atlassian.net/browse/DEB-140) | Implementing Basic Governance | On Hold | Phawhan Saii Gajjalakonda | Medium |
| [DEB-138](https://divami.atlassian.net/browse/DEB-138) | Implementing RAG Cache and updating System prompt | Development in Progress | Maggidi Amulya | Medium |
| [DEB-3](https://divami.atlassian.net/browse/DEB-3) | Implement Jira Connector to Enterprise Brain - V1 (Descriptive Layer) | Start | Rajashekar Gummadidala | Medium |
| [DEB-114](https://divami.atlassian.net/browse/DEB-114) | Planning, Scoping and Cross team discussion | Start | Rajashekar Gummadidala | Medium |
| [DEB-110](https://divami.atlassian.net/browse/DEB-110) | Enterprise Brian should access Internet on User request | On Hold | Phawhan Saii Gajjalakonda | Medium |
| [DEB-97](https://divami.atlassian.net/browse/DEB-97) | Implement User Management with Google Auth | Done | Abhilash Adunuri | Medium |
| [DEB-10](https://divami.atlassian.net/browse/DEB-10) | Implement Intelligence to Enterprise Brain - V1 | Development in Progress | Rajashekar Gummadidala | Medium |
| [DEB-90](https://divami.atlassian.net/browse/DEB-90) | Implement Conversation State, Feedback & Favourites of User query Managements | Open | Abhilash Adunuri | Medium |
| [DEB-134](https://divami.atlassian.net/browse/DEB-134) | Integrate with connected enterprise chat systems - Microsoft Teams Chat | Start | Unassigned | Medium |
| [DEB-135](https://divami.atlassian.net/browse/DEB-135) | Integrate with connected enterprise chat systems - Slack | Start | Unassigned | Medium |
| [DEB-136](https://divami.atlassian.net/browse/DEB-136) | Integrate with connected Email inboxes - Microsoft Outlook | Start | Unassigned | Medium |
| [DEB-137](https://divami.atlassian.net/browse/DEB-137) | Integrate with connected cloud storage systems - Amazon S3 | Start | Unassigned | Medium |
| [DEB-133](https://divami.atlassian.net/browse/DEB-133) | Integrate with connected cloud storage system - One Drive | Start | Unassigned | Medium |
| [DEB-132](https://divami.atlassian.net/browse/DEB-132) | Implement smart search capabilities | Start | Unassigned | Medium |
| [DEB-131](https://divami.atlassian.net/browse/DEB-131) | Performance Optimisation | Start | Unassigned | Medium |
| [DEB-130](https://divami.atlassian.net/browse/DEB-130) | Configure data source syncing | Start | Unassigned | Medium |
| [DEB-129](https://divami.atlassian.net/browse/DEB-129) | Interpret Meeting Transcripts | Start | Unassigned | Medium |
| [DEB-128](https://divami.atlassian.net/browse/DEB-128) | Integrate with online meeting software | Start | Unassigned | Medium |
| [DEB-127](https://divami.atlassian.net/browse/DEB-127) | Integrate with enterprise systems | Start | Unassigned | Medium |
| [DEB-126](https://divami.atlassian.net/browse/DEB-126) | Implement a mechanism to configure one or more DB connectors with chat interface | Start | Unassigned | Medium |
| [DEB-125](https://divami.atlassian.net/browse/DEB-125) | Integrate with connected enterprise collaborative documentation applications | Start | Unassigned | Medium |
| [DEB-75](https://divami.atlassian.net/browse/DEB-75) | Integrate with connected enterprise chat system - Google Chat | Done | Phawhan Saii Gajjalakonda | Medium |
| [DEB-65](https://divami.atlassian.net/browse/DEB-65) | Integrate with connected Email inboxes - Corporate Email | Done | Phawhan Saii Gajjalakonda | Medium |
| [DEB-118](https://divami.atlassian.net/browse/DEB-118) | Application should be able to provide responses from Internet | Start | Phawhan Saii Gajjalakonda | Medium |
| [DEB-117](https://divami.atlassian.net/browse/DEB-117) | RBAC: Users are provided responses based on their access levels | Start | Unassigned | Medium |
| [DEB-54](https://divami.atlassian.net/browse/DEB-54) | Integrate with connected cloud storage system - Google Drive | Done | Phawhan Saii Gajjalakonda | High |
| [DEB-52](https://divami.atlassian.net/browse/DEB-52) | Integrate with the connected Database | Done | Abhilash Adunuri | High |
| [DEB-41](https://divami.atlassian.net/browse/DEB-41) | Chat-like interface for users to query in natural language and to present response | Done | Phawhan Saii Gajjalakonda | High |

## Detailed Breakdown

### [DEB-379](https://divami.atlassian.net/browse/DEB-379): Training and Learning Lifecycle

> RAG DB should be updated with the new training lessons

📄 **Full LLD:** [deb-379-training-and-learning-lifecycle.md](../../phase-2/llds/deb-379-training-and-learning-lifecycle.md)

---

### [DEB-378](https://divami.atlassian.net/browse/DEB-378): Refresh Insights and Escalation Lifecycle

> Receive refresh ping

📄 **Full LLD:** [deb-378-refresh-insights-and-escalation-lifecycle.md](../../phase-2/llds/deb-378-refresh-insights-and-escalation-lifecycle.md)

---

### [DEB-377](https://divami.atlassian.net/browse/DEB-377): Refresh Agent Lifecycle

> Refresh Mechanism & Triggering Scheduler Jobs

📄 **Full LLD:** [deb-377-refresh-agent-lifecycle.md](../../phase-2/llds/deb-377-refresh-agent-lifecycle.md)

---

### [DEB-370](https://divami.atlassian.net/browse/DEB-370): Training Lifecycle

> When trainer updates a runbook, it should maintain versions instead of updating the exisiting runbook and the system should abide to the latest runbook.

📄 **Full LLD:** [deb-370-training-lifecycle.md](../../phase-2/llds/deb-370-training-lifecycle.md)

---

### [DEB-366](https://divami.atlassian.net/browse/DEB-366): Alert Lifecycle (Agent to understand Escallations)

> System should auto understand the escalation from the data snapshot of the most recent refresh and trigger an alert and it should send an email/whatsapp to the user and also udpate the dashboard in th

📄 **Full LLD:** [deb-366-alert-lifecycle-agent-to-understand-escallations.md](../../phase-2/llds/deb-366-alert-lifecycle-agent-to-understand-escallations.md)

---

### [DEB-364](https://divami.atlassian.net/browse/DEB-364): Data Source Agent: REST API Adaptor

> Agent should be able to fetch from data from the APIs using a common REST API Adaptor.

📄 **Full LLD:** [deb-364-data-source-agent-rest-api-adaptor.md](../../phase-2/llds/deb-364-data-source-agent-rest-api-adaptor.md)

---

### [DEB-362](https://divami.atlassian.net/browse/DEB-362): Data Source Agent: Adhoc Query Lifecycle - II

> Implementation of RAG Cache and Testing it out (GMail)

📄 **Full LLD:** [deb-362-data-source-agent-adhoc-query-lifecycle-ii.md](../../phase-2/llds/deb-362-data-source-agent-adhoc-query-lifecycle-ii.md)

---

### [DEB-360](https://divami.atlassian.net/browse/DEB-360): Data Source Agent: Adhoc Query Lifecycle - I

> Implementation of the datasource and DB data sync (GMail)

📄 **Full LLD:** [deb-360-data-source-agent-adhoc-query-lifecycle-i.md](../../phase-2/llds/deb-360-data-source-agent-adhoc-query-lifecycle-i.md)

---

### [DEB-353](https://divami.atlassian.net/browse/DEB-353): Alert Lifecycle - Backend

> APIs to send mail, whatsapp

📄 **Full LLD:** [deb-353-alert-lifecycle-backend.md](../../phase-2/llds/deb-353-alert-lifecycle-backend.md)

---

### [DEB-348](https://divami.atlassian.net/browse/DEB-348): Training Lifecycle

> User Persona and Trainer Persona - RBAC

📄 **Full LLD:** [deb-348-training-lifecycle.md](../../phase-2/llds/deb-348-training-lifecycle.md)

---

### [DEB-344](https://divami.atlassian.net/browse/DEB-344): Core: Knowledge Base Setup and CRUD operations on Knowledge Base for Org Snapshot & Knowledge Graph

> DB Setup and Tables creation for Org Snapshot

📄 **Full LLD:** [deb-344-core-knowledge-base-setup-and-crud-operations-on-knowledge-base-for-org-.md](../../phase-2/llds/deb-344-core-knowledge-base-setup-and-crud-operations-on-knowledge-base-for-org-.md)

---

### [DEB-340](https://divami.atlassian.net/browse/DEB-340): Core: Knowledge Base Setup and CRUD operations on Knowledge Base for Org Info

> DB Setup and Tables creation for Org Info

📄 **Full LLD:** [deb-340-core-knowledge-base-setup-and-crud-operations-on-knowledge-base-for-org-.md](../../phase-2/llds/deb-340-core-knowledge-base-setup-and-crud-operations-on-knowledge-base-for-org-.md)

---

### [DEB-327](https://divami.atlassian.net/browse/DEB-327): Adhoc Question and Answer Lifecycle - I

> Pydantic Agent setup with A2A protocol

📄 **Full LLD:** [deb-327-adhoc-question-and-answer-lifecycle-i.md](../../phase-2/llds/deb-327-adhoc-question-and-answer-lifecycle-i.md)

---

### [DEB-322](https://divami.atlassian.net/browse/DEB-322): Context Propagation Lifecycle

> Make A2A access additional context from other lifecycles

📄 **Full LLD:** [deb-322-context-propagation-lifecycle.md](../../phase-2/llds/deb-322-context-propagation-lifecycle.md)

---

### [DEB-317](https://divami.atlassian.net/browse/DEB-317): Implement Backend Authentication APIs (Google OAuth & Username/Password)

> Develop Backend APIs for Google OAuth and Username/Password Authentication

📄 **Full LLD:** [deb-317-implement-backend-authentication-apis-google-oauth-usernamepassword.md](../../phase-2/llds/deb-317-implement-backend-authentication-apis-google-oauth-usernamepassword.md)

---

### [DEB-313](https://divami.atlassian.net/browse/DEB-313): Implement Login UI with Feature Flag Support

> Should be able to support Google OAuth and Username/Password authentication

📄 **Full LLD:** [deb-313-implement-login-ui-with-feature-flag-support.md](../../phase-2/llds/deb-313-implement-login-ui-with-feature-flag-support.md)

---

### [DEB-312](https://divami.atlassian.net/browse/DEB-312): Feature Flag implementation for Login type (SSO or Basic Auth)

> Configuration file/Configuration DB to be implemented and that should be readbale by frontend.

📄 **Full LLD:** [deb-312-feature-flag-implementation-for-login-type-sso-or-basic-auth.md](../../phase-2/llds/deb-312-feature-flag-implementation-for-login-type-sso-or-basic-auth.md)

---

### [DEB-311](https://divami.atlassian.net/browse/DEB-311): Finalize UI Architecture and Visualization Libraries

> Analyze both Copilot kit and Simulator POC and have discussions with Venkat, Yeshwanth and Squad leads to finalize on the UI Architecture.

📄 **Full LLD:** [deb-311-finalize-ui-architecture-and-visualization-libraries.md](../../phase-2/llds/deb-311-finalize-ui-architecture-and-visualization-libraries.md)

---

### [DEB-308](https://divami.atlassian.net/browse/DEB-308): Evaluate CopilotKit for Dashboard and Chat Integration

> Research need to be documented, and validated.

📄 **Full LLD:** [deb-308-evaluate-copilotkit-for-dashboard-and-chat-integration.md](../../phase-2/llds/deb-308-evaluate-copilotkit-for-dashboard-and-chat-integration.md)

---

### [DEB-307](https://divami.atlassian.net/browse/DEB-307): Simulator POC

> Discussion with Venkat on UI architecture and visualisation libraries, and fixing on the 4 to 5 data visualisation types needed to start with

📄 **Full LLD:** [deb-307-simulator-poc.md](../../phase-2/llds/deb-307-simulator-poc.md)

---

### [DEB-306](https://divami.atlassian.net/browse/DEB-306): ?

> Prepare a plan and discuss for the Governance Lifecycle - How Agents should respect RBAC

📄 **Full LLD:** [deb-306-.md](../../phase-2/llds/deb-306-.md)

---

### [DEB-305](https://divami.atlassian.net/browse/DEB-305): 0. Create LLD Document and get approval

> Discussion with Venkat on UI architecture and visualisation libraries, and fixing on the 4 to 5 data visualisation types needed to start with

📄 **Full LLD:** [deb-305-0-create-lld-document-and-get-approval.md](../../phase-2/llds/deb-305-0-create-lld-document-and-get-approval.md)

---

### [DEB-304](https://divami.atlassian.net/browse/DEB-304): 0. Create LLD Document and get approval

> Evaluate CopilotKit for Dashboard and Chat Integration.

📄 **Full LLD:** [deb-304-0-create-lld-document-and-get-approval.md](../../phase-2/llds/deb-304-0-create-lld-document-and-get-approval.md)

---

### [DEB-303](https://divami.atlassian.net/browse/DEB-303): Demo Support


📄 **Full LLD:** [deb-303-demo-support.md](../../phase-2/llds/deb-303-demo-support.md)

---

### [DEB-246](https://divami.atlassian.net/browse/DEB-246): test


📄 **Full LLD:** [deb-246-test.md](../../phase-2/llds/deb-246-test.md)

---

### [DEB-244](https://divami.atlassian.net/browse/DEB-244): test


📄 **Full LLD:** [deb-244-test.md](../../phase-2/llds/deb-244-test.md)

---

### [DEB-243](https://divami.atlassian.net/browse/DEB-243): Core Agent Architecture


📄 **Full LLD:** [deb-243-core-agent-architecture.md](../../phase-2/llds/deb-243-core-agent-architecture.md)

---

### [DEB-242](https://divami.atlassian.net/browse/DEB-242): Oracle Unifier Architecture


📄 **Full LLD:** [deb-242-oracle-unifier-architecture.md](../../phase-2/llds/deb-242-oracle-unifier-architecture.md)

---

### [DEB-205](https://divami.atlassian.net/browse/DEB-205): Enterprise Brain UI


📄 **Full LLD:** [deb-205-enterprise-brain-ui.md](../../phase-2/llds/deb-205-enterprise-brain-ui.md)

---

### [DEB-204](https://divami.atlassian.net/browse/DEB-204): Sources identification along with the resposne by agent


📄 **Full LLD:** [deb-204-sources-identification-along-with-the-resposne-by-agent.md](../../phase-2/llds/deb-204-sources-identification-along-with-the-resposne-by-agent.md)

---

### [DEB-203](https://divami.atlassian.net/browse/DEB-203): Query validation layer to validate the queries generated by the agent


📄 **Full LLD:** [deb-203-query-validation-layer-to-validate-the-queries-generated-by-the-agent.md](../../phase-2/llds/deb-203-query-validation-layer-to-validate-the-queries-generated-by-the-agent.md)

---

### [DEB-145](https://divami.atlassian.net/browse/DEB-145): Implementation of Personalisation of the application to individuals

> The system or the agent will have the criteria like how it should behave for a C-suit number or someone or someone in the same persona or like what are all the major data points that particular person

📄 **Full LLD:** [deb-145-implementation-of-personalisation-of-the-application-to-individuals.md](../../phase-2/llds/deb-145-implementation-of-personalisation-of-the-application-to-individuals.md)

---

### [DEB-144](https://divami.atlassian.net/browse/DEB-144): Building the actual simulator that will have the canvas to render the dynamic ineteractive dashboards with AI intelligence


📄 **Full LLD:** [deb-144-building-the-actual-simulator-that-will-have-the-canvas-to-render-the-dy.md](../../phase-2/llds/deb-144-building-the-actual-simulator-that-will-have-the-canvas-to-render-the-dy.md)

---

### [DEB-143](https://divami.atlassian.net/browse/DEB-143): Implementation of Intelligent Dynamic and Interactive Dashboard Simulator

> Implementing a dynamic interactive dashboard simulator by discussing with charge GPT or cloud or using AI tools to see what are all the dynamics or the data visualizations a c-suit member need to see 

📄 **Full LLD:** [deb-143-implementation-of-intelligent-dynamic-and-interactive-dashboard-simulato.md](../../phase-2/llds/deb-143-implementation-of-intelligent-dynamic-and-interactive-dashboard-simulato.md)

---

### [DEB-140](https://divami.atlassian.net/browse/DEB-140): Implementing Basic Governance

> 1. The governance includes implementing the policies for all the tables to see only their own personal data will be reflected while communicating with the agent.

📄 **Full LLD:** [deb-140-implementing-basic-governance.md](../../phase-2/llds/deb-140-implementing-basic-governance.md)

---

### [DEB-138](https://divami.atlassian.net/browse/DEB-138): Implementing RAG Cache and updating System prompt

> The agent should be having a rag cache layer where we will be storing the successful agent responses with user acceptance or some other mechanism into one rag caching layer. When user ask a new questi

📄 **Full LLD:** [deb-138-implementing-rag-cache-and-updating-system-prompt.md](../../phase-2/llds/deb-138-implementing-rag-cache-and-updating-system-prompt.md)

---

### [DEB-3](https://divami.atlassian.net/browse/DEB-3): Implement Jira Connector to Enterprise Brain - V1 (Descriptive Layer)


📄 **Full LLD:** [deb-3-implement-jira-connector-to-enterprise-brain-v1-descriptive-layer.md](../../phase-2/llds/deb-3-implement-jira-connector-to-enterprise-brain-v1-descriptive-layer.md)

---

### [DEB-114](https://divami.atlassian.net/browse/DEB-114): Planning, Scoping and Cross team discussion


📄 **Full LLD:** [deb-114-planning-scoping-and-cross-team-discussion.md](../../phase-2/llds/deb-114-planning-scoping-and-cross-team-discussion.md)

---

### [DEB-110](https://divami.atlassian.net/browse/DEB-110): Enterprise Brian should access Internet on User request


📄 **Full LLD:** [deb-110-enterprise-brian-should-access-internet-on-user-request.md](../../phase-2/llds/deb-110-enterprise-brian-should-access-internet-on-user-request.md)

---

### [DEB-97](https://divami.atlassian.net/browse/DEB-97): Implement User Management with Google Auth


📄 **Full LLD:** [deb-97-implement-user-management-with-google-auth.md](../../phase-2/llds/deb-97-implement-user-management-with-google-auth.md)

---

### [DEB-10](https://divami.atlassian.net/browse/DEB-10): Implement Intelligence to Enterprise Brain - V1

> Brining the Enterprise Brain to have the intelligence to choose among the scources and provide the solution based on the users intent.

📄 **Full LLD:** [deb-10-implement-intelligence-to-enterprise-brain-v1.md](../../phase-2/llds/deb-10-implement-intelligence-to-enterprise-brain-v1.md)

---

### [DEB-90](https://divami.atlassian.net/browse/DEB-90): Implement Conversation State, Feedback & Favourites of User query Managements


📄 **Full LLD:** [deb-90-implement-conversation-state-feedback-favourites-of-user-query-management.md](../../phase-2/llds/deb-90-implement-conversation-state-feedback-favourites-of-user-query-management.md)

---

### [DEB-134](https://divami.atlassian.net/browse/DEB-134): Integrate with connected enterprise chat systems - Microsoft Teams Chat

> As a user I should be able to query for information, using natural language prompts, that is present in the enterprise chat systems - Microsoft Teams and that the application should be able to fetch t

📄 **Full LLD:** [deb-134-integrate-with-connected-enterprise-chat-systems-microsoft-teams-chat.md](../../phase-2/llds/deb-134-integrate-with-connected-enterprise-chat-systems-microsoft-teams-chat.md)

---

### [DEB-135](https://divami.atlassian.net/browse/DEB-135): Integrate with connected enterprise chat systems - Slack

> As a user I should be able to query for information, using natural language prompts, that is present in the enterprise chat systems - Slack and that the application should be able to fetch the relevan

📄 **Full LLD:** [deb-135-integrate-with-connected-enterprise-chat-systems-slack.md](../../phase-2/llds/deb-135-integrate-with-connected-enterprise-chat-systems-slack.md)

---

### [DEB-136](https://divami.atlassian.net/browse/DEB-136): Integrate with connected Email inboxes - Microsoft Outlook

> As a user, I should be able to query for information, using natural language prompts, and that the system should be able to fetch that information from the Email inboxes - Microsoft Outlook, that I ha

📄 **Full LLD:** [deb-136-integrate-with-connected-email-inboxes-microsoft-outlook.md](../../phase-2/llds/deb-136-integrate-with-connected-email-inboxes-microsoft-outlook.md)

---

### [DEB-137](https://divami.atlassian.net/browse/DEB-137): Integrate with connected cloud storage systems - Amazon S3

> As a user, I should be able to query for information, using natural language prompts, that is present in any of the shared files/folders within the cloud storage systems - Amazon S3. Along with the re

📄 **Full LLD:** [deb-137-integrate-with-connected-cloud-storage-systems-amazon-s3.md](../../phase-2/llds/deb-137-integrate-with-connected-cloud-storage-systems-amazon-s3.md)

---

### [DEB-133](https://divami.atlassian.net/browse/DEB-133): Integrate with connected cloud storage system - One Drive

> As a user, I should be able to query for information, using natural language prompts, that is present in any of the shared files/folders within the cloud storage systems - One Drive. Along with the re

📄 **Full LLD:** [deb-133-integrate-with-connected-cloud-storage-system-one-drive.md](../../phase-2/llds/deb-133-integrate-with-connected-cloud-storage-system-one-drive.md)

---

### [DEB-132](https://divami.atlassian.net/browse/DEB-132): Implement smart search capabilities

> Application should be able to figure out, based on the given query, what data source to pick first for conducting the search and return the response.

📄 **Full LLD:** [deb-132-implement-smart-search-capabilities.md](../../phase-2/llds/deb-132-implement-smart-search-capabilities.md)

---

### [DEB-131](https://divami.atlassian.net/browse/DEB-131): Performance Optimisation

> Application should be able to respond to user queries in less time (Eg. less than 3 seconds). It should be able to display the progress if it exceeds the set time limit (Eg. Searching in DB… Not Found

📄 **Full LLD:** [deb-131-performance-optimisation.md](../../phase-2/llds/deb-131-performance-optimisation.md)

---

### [DEB-130](https://divami.atlassian.net/browse/DEB-130): Configure data source syncing

> Admin should be able to define data source syncing capabilities to define automated-periodic syncing vs manual syncing.

📄 **Full LLD:** [deb-130-configure-data-source-syncing.md](../../phase-2/llds/deb-130-configure-data-source-syncing.md)

---

### [DEB-129](https://divami.atlassian.net/browse/DEB-129): Interpret Meeting Transcripts

> Application should be able to retrieve information, to user’s queries in natural language, by reading the Meeting Transcripts, Meeting Recordings.

📄 **Full LLD:** [deb-129-interpret-meeting-transcripts.md](../../phase-2/llds/deb-129-interpret-meeting-transcripts.md)

---

### [DEB-128](https://divami.atlassian.net/browse/DEB-128): Integrate with online meeting software

> Application should be able to connect to configured online meeting software (Eg. Google Meeting, Microsoft Teams, Zoom, etc.) as a participant to capture the meeting transcription and along with meeti

📄 **Full LLD:** [deb-128-integrate-with-online-meeting-software.md](../../phase-2/llds/deb-128-integrate-with-online-meeting-software.md)

---

### [DEB-127](https://divami.atlassian.net/browse/DEB-127): Integrate with enterprise systems

> Users should be able to query for information, using natural language prompts, so that the application can retrieve relevant information from the connected enterprise software (Eg. CRMs, HCMs, ERPs, e

📄 **Full LLD:** [deb-127-integrate-with-enterprise-systems.md](../../phase-2/llds/deb-127-integrate-with-enterprise-systems.md)

---

### [DEB-126](https://divami.atlassian.net/browse/DEB-126): Implement a mechanism to configure one or more DB connectors with chat interface

> Application should have the ability to connect to more than one Database systems of different vendors (Eg. MySQL, Postgres, SQL Server, Oracle etc.), so that it can retrieve the response from there.

📄 **Full LLD:** [deb-126-implement-a-mechanism-to-configure-one-or-more-db-connectors-with-chat-i.md](../../phase-2/llds/deb-126-implement-a-mechanism-to-configure-one-or-more-db-connectors-with-chat-i.md)

---

### [DEB-125](https://divami.atlassian.net/browse/DEB-125): Integrate with connected enterprise collaborative documentation applications

> As a user I should be able to query for information, using natural language prompts, within the configured collaborative documentation applications (Eg. Notion, Google Docs, Confluence, etc.), and tha

📄 **Full LLD:** [deb-125-integrate-with-connected-enterprise-collaborative-documentation-applicat.md](../../phase-2/llds/deb-125-integrate-with-connected-enterprise-collaborative-documentation-applicat.md)

---

### [DEB-75](https://divami.atlassian.net/browse/DEB-75): Integrate with connected enterprise chat system - Google Chat

> As a user I should be able to query for information, using natural language prompts, that is present in the enterprise chat systems - Google Chat and that the application should be able to fetch the r

📄 **Full LLD:** [deb-75-integrate-with-connected-enterprise-chat-system-google-chat.md](../../phase-2/llds/deb-75-integrate-with-connected-enterprise-chat-system-google-chat.md)

---

### [DEB-65](https://divami.atlassian.net/browse/DEB-65): Integrate with connected Email inboxes - Corporate Email

> As a user, I should be able to query for information, using natural language prompts, and that the system should be able to fetch that information from the Email inboxes (Eg. Outlook, corporate inbox,

📄 **Full LLD:** [deb-65-integrate-with-connected-email-inboxes-corporate-email.md](../../phase-2/llds/deb-65-integrate-with-connected-email-inboxes-corporate-email.md)

---

### [DEB-118](https://divami.atlassian.net/browse/DEB-118): Application should be able to provide responses from Internet

> In scenarios, where the information requested by user is not available with the connected enterprise information repositories, the application should be able to search for it in Internet, and provide 

📄 **Full LLD:** [deb-118-application-should-be-able-to-provide-responses-from-internet.md](../../phase-2/llds/deb-118-application-should-be-able-to-provide-responses-from-internet.md)

---

### [DEB-117](https://divami.atlassian.net/browse/DEB-117): RBAC: Users are provided responses based on their access levels

> The application should review the logged in user’s access privileges over the requested resource (cloud storage / database / emails, etc.) and should provide the requested information only if they hav

📄 **Full LLD:** [deb-117-rbac-users-are-provided-responses-based-on-their-access-levels.md](../../phase-2/llds/deb-117-rbac-users-are-provided-responses-based-on-their-access-levels.md)

---

### [DEB-54](https://divami.atlassian.net/browse/DEB-54): Integrate with connected cloud storage system - Google Drive

> As a user, I should be able to query for information, using natural language prompts, that is present in any of the shared files/folders within the cloud storage systems - Google Drive. Along with the

📄 **Full LLD:** [deb-54-integrate-with-connected-cloud-storage-system-google-drive.md](../../phase-2/llds/deb-54-integrate-with-connected-cloud-storage-system-google-drive.md)

---

### [DEB-52](https://divami.atlassian.net/browse/DEB-52): Integrate with the connected Database

> As a user I should be able to query for information present in the connected DB using natural language prompts, and the system should interpret the query and provide response in text / table / graphic

📄 **Full LLD:** [deb-52-integrate-with-the-connected-database.md](../../phase-2/llds/deb-52-integrate-with-the-connected-database.md)

---

### [DEB-41](https://divami.atlassian.net/browse/DEB-41): Chat-like interface for users to query in natural language and to present response

> As an end user, logged into the application using my corporate email ID, I should be able to talk to the application via text and voice to query for any information in natural language, and the applic

📄 **Full LLD:** [deb-41-chat-like-interface-for-users-to-query-in-natural-language-and-to-present.md](../../phase-2/llds/deb-41-chat-like-interface-for-users-to-query-in-natural-language-and-to-present.md)

---