Rover MCP Server

# Red Hat Internal Tools - Overview & Use Cases ## Table of Contents 1. [Tool Overview](#tool-overview) 2. [Use Case Categories](#use-case-categories) 3. [Detailed Use Cases](#detailed-use-cases) 4. [Workflow Examples](#workflow-examples) 5. [Best Practices](#best-practices) 6. [Troubleshooting Scenarios](#troubleshooting-scenarios) --- ## Tool Overview ### 🔧 Available Tool Categories #### **Rover Integration Tools** - **Real-time group management data** - **Authoritative membership information** - **Direct Red Hat internal system access** #### **JIRA-Snowflake Integration Tools** - **Historical issue analysis** - **Project activity tracking** - **Cross-team collaboration insights** --- ## Tool Inventory | **Tool Name** | **Purpose** | **Data Type** | **Best Use Case** | |---------------|-------------|---------------|-------------------| | `mcp_rover_rover_group` | Group details lookup | Real-time | Team structure analysis | | `mcp_rover_get_comprehensive_member_profile` | Member analysis | Real-time | Individual contributor assessment | | `mcp_rover_rover_integration_help` | Documentation | Static | Tool usage guidance | | `mcp_jira-mcp-snowflake_list_jira_issues` | Issue search | Historical | Project activity analysis | | `mcp_jira-mcp-snowflake_get_jira_issue_details` | Issue details | Historical | Deep-dive investigation | | `mcp_jira-mcp-snowflake_get_jira_project_summary` | System overview | Historical | Cross-project analysis | | `mcp_jira-mcp-snowflake_list_jira_components` | Component listing | Historical | Project structure analysis | --- ## Use Case Categories ### 🎯 **Category 1: Team Discovery & Analysis** **Objective**: Understand team structures, ownership, and responsibilities ### 🔍 **Category 2: Individual Contributor Assessment** **Objective**: Analyze individual roles, expertise, and project involvement ### 📊 **Category 3: Project & Product Analysis** **Objective**: Understand project scope, team involvement, and activity patterns ### 🔗 **Category 4: Cross-Team Collaboration Mapping** **Objective**: Identify collaboration patterns and shared responsibilities ### 🚀 **Category 5: Infrastructure & Platform Analysis** **Objective**: Understand platform teams, infrastructure ownership, and technical domains --- ## Detailed Use Cases ### 🎯 **Use Case 1: New Team Member Onboarding** **Scenario**: HR or manager needs to understand what teams a new hire should join **Workflow**: ``` 1. Search for product-related groups: "product-qe", "product-dev" 2. Analyze group membership and ownership structure 3. Cross-reference with JIRA activity to understand team responsibilities 4. Identify key contacts and team leads ``` **Tools Used**: - `mcp_rover_rover_group` → Group discovery - `mcp_rover_get_comprehensive_member_profile` → Key member analysis - `mcp_jira-mcp-snowflake_list_jira_issues` → Project context **Real Example**: - **Input**: "3scale-qe-infra" - **Output**: Team structure, 4 members, infrastructure focus, mjaros as lead --- ### 🔍 **Use Case 2: Expertise Location** **Scenario**: Need to find who has expertise in specific technology or product **Workflow**: ``` 1. Search JIRA for technology mentions (e.g., "Jenkins", "CNV", "Camel-K") 2. Identify most active contributors from issue ownership 3. Get comprehensive profiles of key contributors 4. Map to their group memberships for team context ``` **Tools Used**: - `mcp_jira-mcp-snowflake_list_jira_issues` → Activity search - `mcp_rover_get_comprehensive_member_profile` → Expertise analysis - `mcp_rover_rover_group` → Team context **Real Example**: - **Input**: "ansible jenkins" - **Output**: Found ansible-jenkins-admins group, identified smcdonal and olebaran as experts --- ### 📊 **Use Case 3: Project Health Assessment** **Scenario**: Management wants to understand project activity and team engagement **Workflow**: ``` 1. List recent project issues by priority and status 2. Analyze issue assignment patterns and resolution rates 3. Identify key contributors and their group affiliations 4. Assess cross-team collaboration patterns ``` **Tools Used**: - `mcp_jira-mcp-snowflake_list_jira_issues` → Project activity - `mcp_jira-mcp-snowflake_get_jira_project_summary` → Overall health - `mcp_rover_get_comprehensive_member_profile` → Team analysis **Real Example**: - **Input**: "INTEROP" project - **Output**: Active testing project, 50+ issues, sprint-based work, multi-product focus --- ### 🔗 **Use Case 4: Organizational Restructuring** **Scenario**: Planning team reorganization or understanding reporting structures **Workflow**: ``` 1. Map all groups related to product area 2. Analyze overlap in membership across groups 3. Identify key coordinators and shared responsibilities 4. Assess JIRA collaboration patterns ``` **Tools Used**: - `mcp_rover_rover_group` → Multiple group analysis - `mcp_jira-mcp-snowflake_list_jira_issues` → Collaboration patterns - `mcp_rover_get_comprehensive_member_profile` → Individual analysis **Real Example**: - **Input**: CNV-related teams - **Output**: Discovered 7 specialized sub-teams, clear ownership boundaries --- ### 🚀 **Use Case 5: Incident Response** **Scenario**: System outage requires identifying responsible teams and escalation paths **Workflow**: ``` 1. Search for recent issues related to affected component 2. Identify responsible groups and current ownership 3. Get contact information and escalation paths 4. Analyze recent activity for context ``` **Tools Used**: - `mcp_jira-mcp-snowflake_list_jira_issues` → Recent activity - `mcp_rover_rover_group` → Responsible teams - `mcp_jira-mcp-snowflake_get_jira_issue_details` → Specific issue context --- ### 🎯 **Use Case 6: Skill Gap Analysis** **Scenario**: Understanding what expertise exists vs. what's needed for new projects **Workflow**: ``` 1. Search for existing expertise in technology area 2. Map current contributors and their availability 3. Identify groups that should be involved 4. Assess cross-training opportunities ``` **Tools Used**: - `mcp_jira-mcp-snowflake_list_jira_issues` → Current expertise - `mcp_rover_get_comprehensive_member_profile` → Individual skills - `mcp_rover_rover_group` → Team capabilities --- ## Workflow Examples ### **Example A: Complete Team Analysis** ``` Scenario: New manager needs to understand the Ansible infrastructure team Step 1: Group Discovery → mcp_rover_rover_group(group_name="ansible-jenkins-admins") Result: 13 members, 4 owners, self-service group Step 2: Key Member Analysis → mcp_rover_get_comprehensive_member_profile(member_id="smcdonal") → mcp_rover_get_comprehensive_member_profile(member_id="olebaran") Result: Release engineering focus, Jenkins expertise Step 3: Project Context → mcp_jira-mcp-snowflake_list_jira_issues(search_text="ansible jenkins") Result: Migration projects, infrastructure maintenance Step 4: Cross-Reference → mcp_jira-mcp-snowflake_list_jira_issues(search_text="smcdonal") Result: Build engineering, container delivery expertise ``` ### **Example B: Product Team Discovery** ``` Scenario: Understanding who works on 3scale product Step 1: Product Search → mcp_jira-mcp-snowflake_list_jira_issues(project="THREESCALE") Result: Active development project, security focus Step 2: Group Investigation → mcp_rover_rover_group(group_name="3scale-qe-infra") Result: QE infrastructure team, 4 members Step 3: Leadership Analysis → mcp_rover_get_comprehensive_member_profile(member_id="mjaros") Result: Technical lead, documentation focus, container delivery Step 4: Related Projects → mcp_jira-mcp-snowflake_list_jira_issues(search_text="mjaros") Result: SPMM, RCM, DPP project involvement ``` ### **Example C: Technology Expertise Mapping** ``` Scenario: Finding CNV (Container Native Virtualization) experts Step 1: Technology Search → mcp_jira-mcp-snowflake_list_jira_issues(search_text="CNV") Result: Active project with 30+ recent issues Step 2: Project Analysis → mcp_jira-mcp-snowflake_list_jira_issues(project="CNV") Result: 7 specialized teams, tier-based testing Step 3: Group Discovery Attempts → mcp_rover_rover_group(group_name="cnv") → mcp_rover_rover_group(group_name="cnv-qe") Result: No direct groups found (team structure via JIRA patterns) Step 4: Team Structure Analysis Result: CNV Network Team, CNV UI Team, CNV Infrastructure Team, etc. ``` --- ## Best Practices by Use Case ### **Team Discovery** ✅ **Do**: - Start with product/component name searches - Try multiple naming variations (hyphens, underscores) - Cross-reference group membership with JIRA activity - Look for ownership patterns in issues ❌ **Don't**: - Assume exact group name matches - Rely solely on group membership for expertise assessment - Ignore JIRA activity patterns for team boundaries ### **Individual Assessment** ✅ **Do**: - Use comprehensive member profiles for overview - Search individual's JIRA activity for details - Check multiple projects for complete picture - Note time patterns in activity ❌ **Don't**: - Judge expertise solely on JIRA issue count - Ignore inactive periods (may be working on other projects) - Assume recent activity represents total capability ### **Project Analysis** ✅ **Do**: - Use project-specific searches with filters - Look for patterns in issue ownership and assignment - Check multiple time periods for trends - Cross-reference with group memberships ❌ **Don't**: - Rely on single data source - Ignore historical context - Assume current activity represents project importance --- ## Troubleshooting Scenarios ### **Scenario 1: Group Not Found** **Problem**: `mcp_rover_rover_group` returns "Group not found" **Solutions**: 1. Try naming variations: `product-qe`, `product-team`, `product-infra` 2. Search JIRA for team members first: `mcp_jira-mcp-snowflake_list_jira_issues` 3. Look for email patterns in existing groups 4. Check for acronyms or abbreviations **Example**: - `cnv` → Not found - `container-native-virtualization` → Not found - **Solution**: Found team structure through JIRA project analysis ### **Scenario 2: Limited JIRA Activity** **Problem**: Member profile shows no JIRA activity but person is known to be active **Solutions**: 1. Try different search terms (name variations, email) 2. Search multiple projects they might contribute to 3. Check if they work on projects not in Snowflake data 4. Look for older activity with broader date ranges **Example**: - Direct name search yields no results - Try email prefix or variations - Check group membership for project hints ### **Scenario 3: Conflicting Information** **Problem**: Rover groups and JIRA activity don't align **Solutions**: 1. Remember Rover is real-time, JIRA is historical 2. Check dates of JIRA activity vs. current group membership 3. People may have changed roles or projects 4. Cross-reference multiple data sources ### **Scenario 4: Too Much Data** **Problem**: Search returns overwhelming number of results **Solutions**: 1. Add project filters to narrow scope 2. Use time-based filtering for recent activity 3. Focus on specific issue types or priorities 4. Use status filters to focus on active work --- ## Advanced Use Case Patterns ### **Pattern 1: Cross-Product Integration** When working on projects that span multiple products: 1. Map all related groups and projects 2. Identify shared contributors 3. Look for integration-specific teams (like INTEROP) 4. Check for cross-project issue references ### **Pattern 2: Historical Analysis** For understanding how teams evolved: 1. Use date-based JIRA searches across multiple periods 2. Track membership changes in groups over time 3. Look for project transitions and ownership changes 4. Identify skill migration patterns ### **Pattern 3: Compliance & Auditing** For understanding access and responsibilities: 1. Map group memberships to project access 2. Check group approval types and ownership 3. Verify project activity matches group purpose 4. Identify potential access inconsistencies ### **Pattern 4: Strategic Planning** For organizational planning and resource allocation: 1. Analyze workload distribution across teams 2. Identify collaboration bottlenecks 3. Map expertise coverage and gaps 4. Plan for succession and knowledge transfer --- ## Integration Workflows ### **Rover + JIRA Integration Pattern** ``` 1. Start with Rover for current team structure 2. Use JIRA for historical context and activity 3. Cross-reference for complete picture 4. Validate findings across both sources ``` ### **Project-First vs. People-First Approaches** **Project-First**: Start with JIRA project analysis, then find responsible teams **People-First**: Start with group membership, then analyze their project involvement ### **Continuous Monitoring Pattern** ``` 1. Set up regular queries for key teams/projects 2. Track changes in membership and activity 3. Monitor for new groups or project emergence 4. Maintain awareness of organizational changes ``` This document provides a comprehensive framework for leveraging Red Hat's internal tools for various organizational, technical, and strategic purposes.