Bug Creation (EXAMPLE-PROJ)
Create bugs in JIRA using the user's established format. Always confirm the draft with the user before submitting.
Summary Format
{Platform}| {Module}| {Bug title}
- Platform:
iOS or AOS
- Module: Area of the app (e.g.,
Profile, Cart, Checkout, Home, PDP, Search, Favorites, Inbox, Settings)
- Title: Short description of the bug
- Example:
iOS| Profile| Bio field truncates copy after first line from the Edit Profile Page
Description Format (JIRA Wiki Markup)
Use this exact template — fill in values from what the user tells you:
Does this happen in PROD? *{Yes/No}*
Does this happen in {other_platform}? *{Yes/No}*
How reproducible? *{X out of 5}*
Limited to specific devices only? *{Yes/No}*
Limited to specific OS versions only? *{Yes/No}*
Locale/ Language Specific? *{Yes/No}*
*{build_label}* : {version} - {build_number}
{*}Steps{*}:
# Step 1
# Step 2
# Step 3
*Expected:*
* {What should happen}
*Actual:*
* {What actually happens}
{*}Video{*}: [^{filename}]
{additional_notes}
Field rules
{other_platform}: If the bug is on iOS, ask "Does this happen in Android?" — if it's on AOS, ask "Does this happen in iOS?"{build_label}: Use *prod version* if tested on prod, or *build version* for test builds{additional_notes}: Include related tickets (e.g., "also observed in EXAMPLE-PROJ-12279"), older builds tested, or any extra context. Leave blank if none.- Video/Screenshot line: Use
{*}Video{*} or {*}Screenshot{*} depending on what the user attaches. Omit the line if no attachment.
JIRA Fields
| Field |
Value |
| Project |
EXAMPLE-PROJ |
| Issue type |
Bug |
| Priority |
Always TBD (PO sets this) |
| Component |
Based on the module/area (e.g., Profile, Cart) |
Linking Related Tickets
If the user mentions a related ticket, link it using:
Tool: jira_create_issue_link
Args: {
"link_type": "Relates",
"inward_issue_key": "{new_bug_key}",
"outward_issue_key": "{related_ticket_key}"
}
Workflow
- Gather info: From what the user tells you, extract: platform, module, bug title, repro steps, actual/expected, build version, and any related tickets. Ask for anything missing — keep questions short.
- Build the draft: Show the user the full summary + description so they can review and change anything.
- Wait for approval: Do NOT create until the user says go ahead.
- Create the bug: Use
jira_create_issue on user-atlassian-mcp-server with the fields above.
- Link related tickets: If any were mentioned.
- Return the ticket key: So the user can find it.
1---2name: bug-creation3description: Create EXAMPLE-PROJ JIRA bugs in the user's exact format. Use when the user says create bug, file bug, log bug, report bug, raise bug, open bug, write bug, new bug, create issue, file issue, log issue, report issue, raise issue, create defect, file defect, log defect, raise a ticket, create a ticket, or any variation of wanting to create a bug or issue in JIRA.4---56# Bug Creation (EXAMPLE-PROJ)78Create bugs in JIRA using the user's established format. Always confirm the draft with the user before submitting.910## Summary Format1112```13{Platform}| {Module}| {Bug title}14```1516- **Platform**: `iOS` or `AOS`17- **Module**: Area of the app (e.g., `Profile`, `Cart`, `Checkout`, `Home`, `PDP`, `Search`, `Favorites`, `Inbox`, `Settings`)18- **Title**: Short description of the bug19- Example: `iOS| Profile| Bio field truncates copy after first line from the Edit Profile Page`2021## Description Format (JIRA Wiki Markup)2223Use this exact template — fill in values from what the user tells you:2425```26Does this happen in PROD? *{Yes/No}*27Does this happen in {other_platform}? *{Yes/No}*28How reproducible? *{X out of 5}*29Limited to specific devices only? *{Yes/No}*30Limited to specific OS versions only? *{Yes/No}*31Locale/ Language Specific? *{Yes/No}*3233*{build_label}* : {version} - {build_number}3435{*}Steps{*}:36 # Step 137 # Step 238 # Step 33940*Expected:*41 * {What should happen}42 43*Actual:*44 * {What actually happens}45464748{*}Video{*}: [^{filename}]4950{additional_notes}51```5253### Field rules5455- `{other_platform}`: If the bug is on iOS, ask "Does this happen in Android?" — if it's on AOS, ask "Does this happen in iOS?"56- `{build_label}`: Use `*prod version*` if tested on prod, or `*build version*` for test builds57- `{additional_notes}`: Include related tickets (e.g., "also observed in EXAMPLE-PROJ-12279"), older builds tested, or any extra context. Leave blank if none.58- Video/Screenshot line: Use `{*}Video{*}` or `{*}Screenshot{*}` depending on what the user attaches. Omit the line if no attachment.5960## JIRA Fields6162| Field | Value |63|-------|-------|64| Project | `EXAMPLE-PROJ` |65| Issue type | `Bug` |66| Priority | Always `TBD` (PO sets this) |67| Component | Based on the module/area (e.g., `Profile`, `Cart`) |6869## Linking Related Tickets7071If the user mentions a related ticket, link it using:7273```74Tool: jira_create_issue_link75Args: {76 "link_type": "Relates",77 "inward_issue_key": "{new_bug_key}",78 "outward_issue_key": "{related_ticket_key}"79}80```8182## Workflow83841. **Gather info**: From what the user tells you, extract: platform, module, bug title, repro steps, actual/expected, build version, and any related tickets. Ask for anything missing — keep questions short.852. **Build the draft**: Show the user the full summary + description so they can review and change anything.863. **Wait for approval**: Do NOT create until the user says go ahead.874. **Create the bug**: Use `jira_create_issue` on `user-atlassian-mcp-server` with the fields above.885. **Link related tickets**: If any were mentioned.896. **Return the ticket key**: So the user can find it.
vikenpatel14