name: email2jira
description: Convert incoming email requests to Jira tickets for Team China DevSecOps. Use this skill when the user asks to check emails for requests, process DevSecOps requests from email, create Jira tickets from emails, or mentions "email2jira", "email to jira", "request emails", or wants to triage incoming requests sent to Team China DevSecOps. Also trigger when the user mentions checking inbox for team requests or converting email requests to tickets.

Email to Jira Ticket Workflow

This skill monitors Outlook emails for requests sent to Team China DevSecOps and creates corresponding Jira tickets in the CDTT project.

When to Use

• User asks to "check emails for requests" or "process email requests"
• User wants to create Jira tickets from incoming emails
• User mentions Team China DevSecOps email requests
• User asks to triage or handle incoming requests

Workflow

Step 1: Search for Request Emails

Search Outlook for emails matching these criteria:

• Subject contains "request" (case-insensitive)
• Recipients (To or CC) include "Team China DevSecOps"

Use the Outlook MCP tools:

outlook_outlook_search_emails with query: "request"

Then filter results to only include emails where:

• The to or cc field contains "Team China DevSecOps" or "devsecops" (the team's email alias)
• The email hasn't already been processed (check for existing Jira tickets with the same subject)

Step 2: Read and Understand Each Email

For each matching email:

1. Get the full email content using outlook_outlook_get_email_content
2. Extract key information:
   • Requester: The sender's name and email
   • Subject: Email subject line (will become Jira summary)
   • Request Details: The email body content
   • Date: When the request was received
   • Attachments: Note if there are any attachments

Step 3: Get Active Sprint

Before creating tickets, find the current active sprint for the CDTT project:

get_project_sprints with:
  - project_key: "CDTT"
  - state: "active"

This returns the active sprint(s). Use the first active sprint found for ticket assignment.

Step 4: Create Jira Ticket

For each request email, create a Jira Story with:

Project: CDTT
Issue Type: Story
Assignee: XXX(xxx@ford.com) — assigned via jira_assign_issue after creation
Epic Link: CDTT-33xx
Sprint: (use the active sprint name from Step 3)

Summary Format:

[Email Request] {Original Email Subject}

Description Format:

h2. Request Source
*From*: {Sender Name} ({Sender Email})
*Received*: {Email Date}
*Original Subject*: {Subject}

h2. Request Details
{Email Body Content}

----
_This ticket was auto-generated from an email request sent to Team China DevSecOps._

Use the Jira MCP tool:

jira_create_issue with:
  - project_key: "CDTT"
  - issue_type: "Story"
  - summary: "[Email Request] {subject}"
  - description: {formatted description}
  - epic_link: "CDTT-33xx"
  - sprint_name: "{active_sprint_name}"  # from Step 3

Step 5: Assign to XXX

After creating the ticket, assign it using the account email (the assignee parameter in jira_create_issue does not work reliably):

jira_assign_issue with:
  - issue_key: "CDTT-XXXX"
  - assignee_email: "xxx@ford.com"

Step 6: Verify and Fix Sprint Assignment

After creating the ticket, the sprint may not be set correctly due to Jira API limitations. Always verify and fix:

move_to_sprint with:
  - issue_key: "CDTT-XXXX"
  - sprint_name: "{active_sprint_name}"  # from Step 3

This ensures the ticket is added to the active sprint.

Step 7: Mark Email as Processed (Optional)

After successfully creating the Jira ticket:

1. Flag the email using outlook_outlook_flag_email to indicate it's been processed
2. Optionally reply to the sender confirming the ticket was created (ask user first)

Step 8: Report Results

Provide a summary to the user:

• Number of emails found matching criteria
• Number of Jira tickets created
• Active sprint name used
• List of ticket keys with links
• Any emails that couldn't be processed and why

Example Output

Active Sprint: Devops 202606

Found 3 request emails for Team China DevSecOps:

1. "Request: New Jenkins pipeline for Project X"
   From: john.doe@ford.com
   -> Created CDTT-1234, linked to Epic CDTT-3365, added to active sprint

2. "Request: Access to production environment" 
   From: jane.smith@ford.com
   -> Created CDTT-1235, linked to Epic CDTT-3365, added to active sprint

3. "Request: Help with Docker deployment"
   From: bob.wilson@ford.com
   -> Created CDTT-1236, linked to Epic CDTT-3365, added to active sprint

All 3 tickets created, assigned to Jian Liu, linked to Epic CDTT-3365, and added to active sprint (Devops 202606).

Error Handling

• If Outlook search fails, report the error and suggest checking MCP connectivity
• If no active sprint found, warn the user and create ticket without sprint assignment
• If Jira ticket creation fails, save the email details and report which ones failed
• If sprint assignment fails, report the issue but keep the created ticket
• If an email appears to be a duplicate request (similar subject to existing ticket), flag it and ask user before creating

核心发现

核心结论： 团队AI使用成熟度高，年化节省约7,000人时，100%成员认为AI潜力巨大

<!-- _class: dense columns -->

AI工具使用现状

<div>

使用频率

Copilot深度 — 高活跃(≥50%): 13人(57%)

</div>
<div>

工具覆盖率

</div>

<!-- _class: dense columns -->

效果评估

<div>

效果评分 (1-5分)

</div>
<div>

每周节省时间

年化节省：~7,000人时
(23人×6.3h/周×48周)

</div>

<!-- _class: columns -->

障碍与需求分析

<div>

主要障碍 Top 3

其他障碍（整合困难、政策不清等）阻碍程度较低

</div>
<div>

最需要的支持 Top 3

其他：培训课程(39%)、经验分享(30%)

</div>

未来意愿与期望领域

100%成员愿意加大AI使用，100%认为AI潜力巨大

成功案例主题： 代码迁移(.NET升级) · 问题诊断(节省5天) · 成本优化(TMC AWS) · 自动化(Release/Monitor)

行动建议

优先级	时间	行动项	目标
高	2周	发布AI使用合规指南	消除52%隐私顾虑，提升政策了解度
高	1月	建立最佳实践案例库	加速经验传播，满足61%需求
🟡 中	持续	组织Prompt技巧分享会	降低"输出不稳定"感知(当前52%)
🟡 中	3月	扩展AI工具访问权限	满足78%成员最大需求
🟢 低	6月	探索AI Agent工作流	深化自动化，响应26%期望

跟踪指标： 每日使用率(91%→95%) · 高活跃用户(57%→70%) · 政策了解度(57%→80%)

This is what a topic and post looks like. As an administrator, you can edit the post's title and content.
To customise your forum, go to the Administrator Control Panel. You can modify all aspects of your forum there, including installation of third-party plugins.

Additional Resources

• NodeBB Documentation
• Community Support Forum
• Project repository