ifixkart-admin/workflows/sharable/standard/update-clickup-ticket.md
Adithiyan bbd3a3e959 feat: initial commit — full platform snapshot
- Backend: FastAPI app with all models, services, schemas, routes
- Admin Panel: Next.js dashboard with all modules
  (CRM, POS, repairs, warranties, billing, notifications, etc.)
- Ecommerce: storefront (submodule) + product catalog
- AI Agents: .agents/ skill library for Antigravity IDE
- Docs: architecture, billing, notification gateway markdown
- Submodules: Backend/OpenWA, Ecommerce/File 2/storefront
2026-10-13 12:59:47 +05:30

2.1 KiB

description
Update ClickUp ticket with commit changes or custom description

Update ClickUp Ticket

Updates a ClickUp ticket (comment or description) with formatted change information based on recent commits or custom instructions.

Usage

Provide:

  1. ClickUp ticket URL (e.g., https://app.clickup.com/t/86d3cq9j5)
  2. Instruction specifying:
    • Whether to update comment or description
    • What changes to include (e.g., "last 2 commits", "specific feature")
    • QA testing context (e.g., "QA can test by changing type using same modal")

Output Format

The update includes 3 sections in markdown. Keep content concise and balanced — not too brief, not verbose.

Simple Description

1-2 sentences summarizing what changed. Focus on the main outcome.

Why We Need It

1-2 sentences explaining the business reason or problem being solved. Avoid long background stories.

What We Did

Bullet list (3-7 items) of key technical changes. List the most impactful changes, not every detail.

QA Context

1-2 sentences explaining how to test or verify the changes. Include specific steps or scenarios.

Example

@update-clickup-ticket https://app.clickup.com/t/86d3cq9j5 update comment with last 2 commit changes, updated flow for home sale type change, QA can test by changing type using same modal.

Notes

  • Comments support markdown formatting
  • Descriptions do NOT support markdown — use plain text if updating description
  • Always include all 3 sections (description, why, what, QA context)
  • Keep each section concise — the goal is a clear update, not a comprehensive story

Implementation

Use the ClickUp MCP server to update the ticket:

  1. Extract task ID from URL (e.g., 86d3cq9j5 from https://app.clickup.com/t/86d3cq9j5)
  2. Get commit details using git log or git show
  3. Format content according to the 3-section structure above
  4. Use mcp1_clickup_create_comment for comments or update task description for descriptions
  5. Always use markdown formatting for comments; use plain text for descriptions