AI Skill Report Card
Managing JIRA Workflows
Quick Start
Python# Always load tools first tool_search("jira_add_comment otter") otter:jira_add_comment(issue_key="CORE-123", body="Updated analysis complete") # Create and place on Kanban tool_search("jira_create otter") result = otter:jira_create(project_key="CORE", issue_type="Task", summary="Fix data pipeline", description="# Context\nPipeline failing since last deploy") otter:jira_transition_issue(issue_key=result.key, transition_id=81) # Move to Ready (Kanban)
Workflow15 / 15
Standard Task Creation + Kanban Placement
- Load tools:
tool_search("jira_create otter") - Create ticket:
jira_create→ capture key - Link if needed:
jira_link_issues(parallel with create) - Move to Ready:
jira_transition_issue(transition_id=81)→ puts on Kanban - Assign:
jira_update(fields='assignee="61dd904c90cfd200716689de"')
Tool Loading Requirements
CRITICAL: Otter tools must be loaded via tool_search before use.
tool_search("jira_add_comment otter") # Comment tools
tool_search("jira_create otter") # Create + link tools
tool_search("jira get agile boards") # Board + transition tools
tool_search("jira update assignee issue") # Update tool
Core Data Transition IDs (Stable)
- 71 = Backlog
- 81 = Ready ← Use this for Kanban placement
- 31 = In Progress
- 51 = Review
- 61 = Testing
- 91 = Delivered
- 101 = Cancelled
Recommendation▾
Remove the redundant 'tool_search' explanation in the Quick Start - it's repeated in Tool Loading Requirements section
Examples18 / 20
Example 1: Add Comment Input: "Add comment to CORE-456 saying the fix is deployed"
tool_search("jira_add_comment otter")
otter:jira_add_comment(issue_key="CORE-456", body="Fix deployed to production")
Example 2: Create + Link + Kanban
Input: "Create subtask for CORE-789 to update the schema"
tool_search("jira_create otter")
result = otter:jira_create(
project_key="CORE",
issue_type="Task",
summary="Update schema for user events",
description="# Context\nParent ticket CORE-789 needs schema changes\n\n# Goal\nUpdate schema to support new fields"
)
otter:jira_link_issues(inward_issue="CORE-789", outward_issue=result.key, link_type="Relates")
otter:jira_transition_issue(issue_key=result.key, transition_id=81)
Example 3: Batch Comment Input: "Add 'reviewed' comment to CORE-100, CORE-101, CORE-102"
# Parallel execution
for ticket in ["CORE-100", "CORE-101", "CORE-102"]:
otter:jira_add_comment(issue_key=ticket, body="Reviewed ✓")
Recommendation▾
Consolidate the Canva Context section into the workflow where it's actually used rather than as separate reference material
Canva Context
- Primary instance:
https://canva.atlassian.net(default) - Secondary instance:
https://canvadev.atlassian.net(for RISK, INCIDENT projects) - Ken's account ID:
61dd904c90cfd200716689de - Core Data Kanban board ID:
544 - Core Data project:
CORE - DynamoDB backlog epic:
CORE-601
Best Practices
- Tool loading: Always
tool_searchbefore using otter tools - Parallel execution: Run independent operations simultaneously
- Account IDs: Use
61dd904c90cfd200716689defor Ken, not display names - Link types: Case-sensitive ("Relates", "Blocks", "Depends")
- Task hierarchy: Use
jira_link_issues, notparent_keyfor Task→Task in CORE - Description template: Use Context/Goal/Out of scope format for new tasks
Common Pitfalls
- Don't assume tools are loaded - always call
tool_searchfirst - Don't use display names for assignee - requires account ID
- Don't use
parent_keyfor CORE Task→Task hierarchy - use linking instead - Don't run batch operations sequentially when they can be parallel
- Don't assume primary instance - check for 404s and try canvadev instance
- Don't guess field formats -
assigneeneeds quotes,labelsneeds brackets